Triple
T1526900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US-2 eastbound |
E32355
|
entity |
| Predicate | trafficFlow |
P23123
|
FINISHED |
| Object | one-way eastbound carriageway where divided |
—
|
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: one-way eastbound carriageway where divided | Statement: [US-2 eastbound, trafficFlow, one-way eastbound carriageway where divided]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trafficFlow Context triple: [US-2 eastbound, trafficFlow, one-way eastbound carriageway where divided]
-
A.
trafficDirection
Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
-
B.
roadTraffic
chosen
Indicates the presence, flow, or conditions of vehicles and movement along roads or streets.
-
C.
trafficLevel
Indicates the degree of congestion or flow intensity present in a transportation network or route at a given time.
-
D.
annualTraffic
Indicates the typical amount or volume of traffic associated with something over the course of a year.
-
E.
trafficType
Indicates the category or nature of traffic involved in a given interaction, flow, or connection (e.g., type of network, data, or transport traffic).
- 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_69a885e9b0ac819093a9806ad0efc82c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a933ddc5a881909cdf503f2bc29bd4 |
completed | March 5, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69a907ae8f688190ad9000ea1e018585 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.