Triple
T22776320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 20 in Illinois |
E563709
|
entity |
| Predicate | bridgeAtStateLine |
P53076
|
FINISHED |
| Object | Julien Dubuque Bridge |
—
|
NE NERFINISHED |
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: Julien Dubuque Bridge | Statement: [U.S. Route 20 in Illinois, bridgeAtStateLine, Julien Dubuque Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeAtStateLine Context triple: [U.S. Route 20 in Illinois, bridgeAtStateLine, Julien Dubuque Bridge]
-
A.
bridgeLocation
Indicates the specific place or area where a bridge is situated or spans.
-
B.
bridgePosition
Indicates the spatial or structural position of a bridge relative to other referenced elements or locations.
-
C.
bridgeName
Indicates the designated name assigned to a specific bridge.
-
D.
crossesStateBoundaryViaBridgeTo
chosen
Indicates that one entity crosses a state boundary to reach another entity specifically by traveling over a bridge.
-
E.
bridgeCarries
Indicates that a bridge serves as a route or support structure for transporting or conveying something (such as vehicles, pedestrians, or utilities) across an obstacle.
- 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_69e24554497c819080b996e071de27c2 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17b61acf881909d9f54e0966ee3cc |
completed | April 29, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:28 p.m.