Triple
T5062532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 680 |
E114055
|
entity |
| Predicate | bridgeTypeAtRiverCrossing |
P1787
|
FINISHED |
| Object | highway bridge over Missouri River |
—
|
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: highway bridge over Missouri River | Statement: [Interstate 680, bridgeTypeAtRiverCrossing, highway bridge over Missouri River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeTypeAtRiverCrossing Context triple: [Interstate 680, bridgeTypeAtRiverCrossing, highway bridge over Missouri River]
-
A.
bridgeType
chosen
Indicates the specific kind or classification of a bridge associated with an entity.
-
B.
riverCrossingStructure
Indicates a structure that allows passage across a river, such as by spanning or traversing it.
-
C.
bridgeSpans
Indicates that a bridge extends across and connects two separate points or areas.
-
D.
bridgeName
Indicates the designated name assigned to a specific bridge.
-
E.
hasBridgeTypeCrossing
Indicates that a bridge is characterized by a specific type of crossing it provides or supports.
- 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_69bd443c0c8c81908663b77afb28e165 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7475be3c819085cde8ec544c407e |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd715622b48190a3e8e49a5ef62b4a |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:38 p.m.