Triple
T21391894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James B. Edwards Bridge |
E527674
|
entity |
| Predicate | carries |
P1393
|
FINISHED |
| Object | I-526 |
—
|
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: I-526 | Statement: [James B. Edwards Bridge, carries, I-526]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: I-526 Context triple: [James B. Edwards Bridge, carries, I-526]
-
A.
I-526
chosen
I-526 is an auxiliary Interstate Highway serving as a partial beltway around Charleston, South Carolina, connecting major routes and facilitating regional traffic flow.
-
B.
I-520
I-520 is an auxiliary Interstate Highway that forms a partial beltway around Augusta, Georgia and North Augusta, South Carolina.
-
C.
I-229
I-229 is a short auxiliary Interstate Highway in Missouri that serves as a bypass and business route around downtown St. Joseph.
-
D.
I-229
I-229 is an auxiliary Interstate Highway that serves as a bypass route around Sioux Falls in southeastern South Dakota.
-
E.
I-530
I-530 is a short Interstate Highway in Arkansas that connects Little Rock to Pine Bluff, serving as an important regional transportation corridor.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b51ff3748190935c0a513c62a12b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69ee62cbfef08190a33ac1f198c82cd0 |
completed | April 26, 2026, 7:09 p.m. |
Created at: April 16, 2026, 5:13 p.m.