Triple
T997775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sturt Highway |
E21532
|
entity |
| Predicate | hasCarriagewayType |
P22311
|
FINISHED |
| Object | single carriageway |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: single carriageway | Statement: [Sturt Highway, hasCarriagewayType, single carriageway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCarriagewayType Context triple: [Sturt Highway, hasCarriagewayType, single carriageway]
-
A.
roadwayCarries
Indicates that a roadway serves as a route that supports or conveys a particular transportation facility, traffic flow, or designated use.
-
B.
hasLanes
Indicates that an entity, such as a road or pathway, is divided into one or more distinct lanes for traffic or movement.
-
C.
hasExpresswaySection
Indicates that an entity includes, contains, or is associated with a specific section or segment of an expressway.
-
D.
laneCount
Indicates the number of parallel lanes associated with a given road or roadway segment.
-
E.
hasTrafficIsland
Indicates the presence of a traffic island separating or organizing lanes or directions of vehicular movement within a roadway.
- F. None of above. chosen
Provenance (4 batches)
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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4e0f0d081908b888c246d001786 |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2b057c48190b9e42df9246b3757 |
completed | March 1, 2026, 9:42 p.m. |
| PDg | Predicate description generation | batch_69a4b3a02ea481909555cf5b7bed0d9a |
completed | March 1, 2026, 9:46 p.m. |
Created at: March 1, 2026, 7:41 p.m.