Inspect instances in Graph Explorer
What you will learn
Query a collection's entities and relations, then inspect node properties and neighbouring relations.
Inspect the iot_machine, iot_sensor, and iot_reads_from data loaded in the previous lessons. The Data tabs in Modeling show table rows; Graph Explorer shows whether those rows became nodes connected by a directed relation.
Open Graph Explorer
- Select Ontology → Graph Explorer in the left sidebar.
- In the left Graph Structure panel, select the course collection.
- Confirm the expected metadata.
| Section | Expected items |
|---|---|
| Entities | iot_machine, iot_sensor |
| Relations | iot_reads_from |
| Properties | Properties available in the current result |
The 2D / 3D control changes only the visualization of the same result. Start with 2D because nodes and edges are easier to select.
Query entities and relations
- Select
iot_machineunder Entities to query nodes with that label. - Select
iot_reads_fromunder Relations to query the relation with its Source and Target nodes. - Select All in either section to query all entities or all relations in the selected collection.
With the practice data loaded, an entity result can report three nodes and one relation. A relation result should report two nodes and one relation.
Select sensor_001 in the graph. Confirm id in the Node properties panel, then select the edge and confirm its installed_at property.
Expand from one node
Entity and relation selections include one-hop context for the selected type. Use Expand neighbours when you need to move farther from one node.
- Select
machine_001in the graph. - In the Node properties panel, select Expand neighbours.
- If another neighbour is available, the result summary increases. If every neighbour is already visible, Portal reports that no new nodes were found.
- To restore the initial result, select Reset to query result in the right toolbar.
Inspect the result as a table
Select Results in the right toolbar to inspect the current result under Table and Text. Use the graph for direction and connections, then compare node and relation properties in the result panel.
Compare 2D and 3D
Switch the same result between 2D / 3D. 3D can help with spatial exploration of complex connections, but rendering many nodes and relations may show a performance warning. Use 2D first for structural and property checks.
Self-check
iot_machine,iot_sensor, andiot_reads_fromappear for the collection.- Querying the relation shows two nodes and one relation.
- A node was selected and the result of Expand neighbours was checked.
- Both Table and Text results were inspected.
- Relation direction and
installed_atare correct.
Next lesson
Finally, inspect which model changes are supported, assess their impact, and hand analysts reproducible exploration conditions and engineers an exact pipeline output contract.
Before you finish
Use these questions to check whether you achieved this lesson's goal.
- Can you repeat ‘Inspect instances in Graph Explorer’ without following the instructions?
- Can you name at least one place to check when the result differs from what you expected?