Triple
T16977037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-664 |
E411840
|
entity |
| Predicate | beltwayDesignation |
P125459
|
FINISHED |
| Object | western leg of Hampton Roads Beltway |
—
|
LITERAL FINISHED |
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: western leg of Hampton Roads Beltway | Statement: [I-664, beltwayDesignation, western leg of Hampton Roads Beltway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beltwayDesignation Context triple: [I-664, beltwayDesignation, western leg of Hampton Roads Beltway]
-
A.
beltwayName
Indicates that a beltway (ring road or orbital highway) has a specific name.
-
B.
beltwayType
Indicates the specific classification or type of a beltway (ring road) associated with a given roadway or area.
-
C.
beltwayAround
Indicates that one roadway or route functions as a beltway encircling or surrounding another specified area or location.
-
D.
outerBeltwayFor
Indicates that one roadway or route functions as an outer beltway encircling or bypassing the area served by another route or location.
-
E.
trailDesignation
Indicates that a particular label, name, or classification has been assigned to a trail to identify its route, type, or official status.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:32 a.m.