Triple
T21413789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delaware Route 299 |
E528245
|
entity |
| Predicate | terminusEast |
P3569
|
FINISHED |
| Object | U.S. Route 13 in Odessa, Delaware |
—
|
NE NERFINISHED |
How this triple was built (3 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: U.S. Route 13 in Odessa, Delaware | Statement: [Delaware Route 299, terminusEast, U.S. Route 13 in Odessa, Delaware]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: U.S. Route 13 in Odessa, Delaware Context triple: [Delaware Route 299, terminusEast, U.S. Route 13 in Odessa, Delaware]
-
A.
U.S. Route 13 in Pennsylvania
U.S. Route 13 in Pennsylvania is a major north–south highway in the eastern part of the state that serves communities in the Philadelphia metropolitan area, including Falls Township in Bucks County.
-
B.
U.S. Route 13 in Maryland
U.S. Route 13 in Maryland is a major north–south highway on the Delmarva Peninsula that connects communities on the Eastern Shore and serves as a key corridor between Virginia and Delaware.
-
C.
U.S. Route 13 in North Carolina
U.S. Route 13 in North Carolina is a major north–south U.S. Highway that connects rural eastern parts of the state with key regional routes and communities.
-
D.
U.S. Route 130 in New Jersey
U.S. Route 130 in New Jersey is a major north–south highway running through central and southern parts of the state, serving as an important alternative to the New Jersey Turnpike and U.S. Route 1 for regional traffic.
-
E.
U.S. Route 13 in Virginia
U.S. Route 13 in Virginia is a major north–south highway that runs through the eastern part of the state, including the Eastern Shore and the Chesapeake Bay Bridge–Tunnel corridor.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: U.S. Route 13 in Odessa, Delaware Target entity description: U.S. Route 13 in Odessa, Delaware is a major north–south highway corridor through the town, serving as a key local and regional route for traffic in the area.
-
A.
U.S. Route 13 in Pennsylvania
U.S. Route 13 in Pennsylvania is a major north–south highway in the eastern part of the state that serves communities in the Philadelphia metropolitan area, including Falls Township in Bucks County.
-
B.
U.S. Route 13 in Maryland
U.S. Route 13 in Maryland is a major north–south highway on the Delmarva Peninsula that connects communities on the Eastern Shore and serves as a key corridor between Virginia and Delaware.
-
C.
U.S. Route 13 in North Carolina
U.S. Route 13 in North Carolina is a major north–south U.S. Highway that connects rural eastern parts of the state with key regional routes and communities.
-
D.
U.S. Route 130 in New Jersey
U.S. Route 130 in New Jersey is a major north–south highway running through central and southern parts of the state, serving as an important alternative to the New Jersey Turnpike and U.S. Route 1 for regional traffic.
-
E.
U.S. Route 13 in Virginia
U.S. Route 13 in Virginia is a major north–south highway that runs through the eastern part of the state, including the Eastern Shore and the Chesapeake Bay Bridge–Tunnel corridor.
- F. None of above. chosen
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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b201ce1481908392c77e5ca40f5f |
completed | April 22, 2026, 11:33 a.m. |
Created at: April 16, 2026, 5:44 p.m.