Triple
T9224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council Bluffs, Iowa |
E184
|
entity |
| Predicate | transportationLink |
P385
|
FINISHED |
| Object | Highway and bridge connections to Omaha, Nebraska |
—
|
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 and bridge connections to Omaha, Nebraska | Statement: [Council Bluffs, Iowa, transportationLink, Highway and bridge connections to Omaha, Nebraska]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportationLink Context triple: [Council Bluffs, Iowa, transportationLink, Highway and bridge connections to Omaha, Nebraska]
-
A.
transportation
Indicates the movement of someone or something from one place to another, typically using a vehicle or transit system.
-
B.
hasLightRailSystem
Indicates that a place possesses and operates a light rail transit system.
-
C.
hasMajorHighway
chosen
Indicates that a location or area is served by or directly connected to a major highway route.
-
D.
drivesOn
Indicates that an entity uses or travels along a particular route, surface, or roadway as its path of movement.
-
E.
hasStreetcarSystem
Indicates that a place possesses or is served by an operational streetcar (tram) transit system.
- 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_69a23bb612708190b09f25385e4b63d1 |
completed | Feb. 28, 2026, 12:49 a.m. |
| NER | Named-entity recognition | batch_69a240b249788190af8dbf7e80e9c91b |
completed | Feb. 28, 2026, 1:11 a.m. |
| PD | Predicate disambiguation | batch_69a23fe52ec48190a4d24101c91434ed |
completed | Feb. 28, 2026, 1:07 a.m. |
Created at: Feb. 28, 2026, 12:54 a.m.