Triple
T21605247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Songlines |
E533154
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | navigational system |
C28834
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: navigational system Context triple: [Songlines, instanceOf, navigational system]
-
A.
navigation system
chosen
A navigation system is a coordinated set of hardware and software components that determines a user's position and provides optimal routes and guidance to reach desired destinations.
-
B.
navigational passage
A navigational passage is a corridor, channel, or route—often within a building, vessel, or geographic area—designed to guide movement safely and efficiently from one location to another.
-
C.
terrestrial navigation system
A terrestrial navigation system is a ground-based infrastructure and associated equipment that determine a vehicle’s position, velocity, and course using signals or references located on or near the Earth’s surface.
-
D.
autonomous navigation system
An autonomous navigation system is a self-directed control framework that enables vehicles or robots to perceive their environment, plan routes, and move safely to a destination without human intervention.
-
E.
satellite navigation system feature
A satellite navigation system feature is a specific capability or function within a satellite-based positioning system that enhances how location, routing, tracking, or related spatial information is calculated, presented, or used.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e0c46364608190a337dc8720dc2a35 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:33 p.m.