Triple
T3609472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 580 (Nevada) |
E76449
|
entity |
| Predicate | bridgeTypeOnRoute |
P1787
|
FINISHED |
| Object | segmental concrete arch bridge (Galena Creek Bridge) |
—
|
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: segmental concrete arch bridge (Galena Creek Bridge) | Statement: [Interstate 580 (Nevada), bridgeTypeOnRoute, segmental concrete arch bridge (Galena Creek Bridge)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeTypeOnRoute Context triple: [Interstate 580 (Nevada), bridgeTypeOnRoute, segmental concrete arch bridge (Galena Creek Bridge)]
-
A.
bridgeType
chosen
Indicates the specific kind or classification of a bridge associated with an entity.
-
B.
bridgeName
Indicates the designated name assigned to a specific bridge.
-
C.
bridgeLocation
Indicates the specific place or area where a bridge is situated or spans.
-
D.
riverCrossingStructure
Indicates a structure that allows passage across a river, such as by spanning or traversing it.
-
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_69ad85da0ba481908b3b48c69efe2b98 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc22b824c8190a85b36185d4957bb |
completed | March 8, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69adb83d8b1c8190b3bddbc5dc995a87 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.