Triple
T4350122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CTA bus route 152 Addison |
E98002
|
entity |
| Predicate | usesRightHandTraffic |
P250
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [CTA bus route 152 Addison, usesRightHandTraffic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRightHandTraffic Context triple: [CTA bus route 152 Addison, usesRightHandTraffic, true]
-
A.
drivingSide
chosen
Indicates which side of the road (left or right) vehicles are required to drive on in a given jurisdiction.
-
B.
usesRightHandDriveBrandNameInUK
Indicates that the brand name is used in the United Kingdom for vehicles configured with right-hand drive.
-
C.
hasRightOfWay
Indicates that one entity is entitled to proceed or act before another in a shared space or interaction, without having to yield.
-
D.
hasTrafficDirection
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
E.
someRightOfWayUsedBy
Indicates that a particular right of way is utilized or traversed by a specified user, route, or transport entity.
- F. None of above.
Provenance (3 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_69b3454965f881908c41190bb22f0e4b |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351a840248190b88c8a7be9158d25 |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f51ed7c8190b7bf5f44b56b730d |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:15 p.m.