Triple
T16044724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 26 |
E389186
|
entity |
| Predicate | bridgeStructure |
P121738
|
FINISHED |
| Object | multiple interchanges and overpasses |
—
|
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: multiple interchanges and overpasses | Statement: [Interstate 26, bridgeStructure, multiple interchanges and overpasses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeStructure Context triple: [Interstate 26, bridgeStructure, multiple interchanges and overpasses]
-
A.
bridgeType
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.
hasBridgeOrStructure
Indicates that there exists a bridge or similar structural connection between the related entities.
-
E.
bridges
Indicates that one entity connects or links two or more other entities, allowing passage, transition, or interaction between them.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1826f34c081908005bb736f1c485d |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e1ff5cd7e481908a29214139a3de2e |
completed | April 17, 2026, 9:37 a.m. |
Created at: April 10, 2026, 4:56 a.m.