Triple
T31483643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-459/I-20/I-59 interchange (western terminus) |
E803212
|
entity |
| Predicate | partOfBypass |
P12840
|
FINISHED |
| Object | Birmingham beltway I-459 |
—
|
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: Birmingham beltway I-459 | Statement: [I-459/I-20/I-59 interchange (western terminus), partOfBypass, Birmingham beltway I-459]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfBypass Context triple: [I-459/I-20/I-59 interchange (western terminus), partOfBypass, Birmingham beltway I-459]
-
A.
bypassedVia
Indicates that one entity is avoided, skipped, or circumvented by using another specified means, route, or method.
-
B.
hasBypass
chosen
Indicates that one entity includes or is equipped with an alternative route or mechanism that circumvents or avoids another entity or process.
-
C.
bypassType
Indicates the specific kind or method of bypass used to circumvent or route around a normal process, path, or control.
-
D.
bypassesCity
Indicates that a route, road, or path goes around a city rather than passing directly through it.
-
E.
partOfTunnel
Indicates that one entity forms a physical segment or component within the structure or extent of a tunnel.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff519b65f081909902ba83b775ef85 |
completed | May 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69ff506fccdc8190bd93269589040aed |
completed | May 9, 2026, 3:19 p.m. |
Created at: April 30, 2026, 9:34 p.m.