Triple
T16977156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hampton Roads Beltway |
E411842
|
entity |
| Predicate | connectsToU.S.Route |
P39744
|
FINISHED |
| Object | U.S. Route 17 |
—
|
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: U.S. Route 17 | Statement: [Hampton Roads Beltway, connectsToU.S.Route, U.S. Route 17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsToU.S.Route Context triple: [Hampton Roads Beltway, connectsToU.S.Route, U.S. Route 17]
-
A.
servedByU.S.Route
chosen
Indicates that a place or transportation feature is provided access or connectivity by a specific U.S. Route highway.
-
B.
stateRouteConnection
Indicates a relationship where a state-level route connects or links two locations or transportation segments.
-
C.
UShighwayNumber
Indicates that a U.S. highway is identified by a specific route number.
-
D.
connectsNorthTo
Indicates that one entity serves as a connection or link from another entity to something located to its north.
-
E.
isSuburbanRouteOf
Indicates that a given route functions as a suburban segment or service line belonging to, or operating as part of, a larger primary route or network.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d184f2cc81908ac629c8f87696f8 |
completed | April 18, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.