Triple
T19427541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 80 bridges |
E486021
|
entity |
| Predicate | roadDirectionCarried |
P11314
|
FINISHED |
| Object | eastbound traffic |
—
|
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: eastbound traffic | Statement: [Interstate 80 bridges, roadDirectionCarried, eastbound traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadDirectionCarried Context triple: [Interstate 80 bridges, roadDirectionCarried, eastbound traffic]
-
A.
roadwayCarries
chosen
Indicates that a roadway serves as a route that supports or conveys a particular transportation facility, traffic flow, or designated use.
-
B.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
C.
routeDirectionB
Indicates that one entity represents the direction or orientation of a route or path relative to another entity.
-
D.
routeDirectionA
Indicates the primary or first directional orientation or heading associated with a specific route.
-
E.
roadTraverses
Indicates that a road passes through, crosses, or extends across a specified geographic area or feature.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6321abb9c81908ad73c2cd537d0f1 |
completed | April 20, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.