Triple
T6747853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inner Loop |
E154263
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | roadway traffic direction designation |
C8909
|
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: roadway traffic direction designation Context triple: [Inner Loop, instanceOf, roadway traffic direction designation]
-
A.
highway direction
chosen
A highway direction represents the designated orientation or route of travel along a highway, typically indicated by cardinal or ordinal compass points (e.g., northbound, southeast).
-
B.
road designation
A road designation is a label or code assigned to a roadway (such as a route number, name, or classification) that identifies its function, hierarchy, and navigational role within a transportation network.
-
C.
road traffic agreement
A road traffic agreement is a formal arrangement between parties—such as governments, municipalities, or private entities—that defines rights, responsibilities, and rules for the use, management, and regulation of road traffic within a specified area or network.
-
D.
road segment
A road segment is a continuous portion of a roadway between two defined endpoints, such as intersections or junctions, characterized by uniform attributes like direction, number of lanes, and speed limit.
-
E.
traffic authority
A traffic authority is an organization or governmental body responsible for planning, regulating, and managing road use, traffic flow, and transportation safety within a specific jurisdiction.
- 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_69c6880ef37881909268a5a7299b9293 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:11 p.m.