Triple
T9638745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linn Cove Viaduct |
E233002
|
entity |
| Predicate | blueRidgeParkwayMilepost |
P89390
|
FINISHED |
| Object | 304.4 |
—
|
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: 304.4 | Statement: [Linn Cove Viaduct, blueRidgeParkwayMilepost, 304.4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blueRidgeParkwayMilepost Context triple: [Linn Cove Viaduct, blueRidgeParkwayMilepost, 304.4]
-
A.
trailMilepostOn
Indicates that a specific milepost is physically located on and associated with a particular trail segment or trail route.
-
B.
beltwayName
Indicates that a beltway (ring road or orbital highway) has a specific name.
-
C.
nearbyHighwayMilepost
Indicates that one entity is located close to a specific highway milepost associated with another entity.
-
D.
beltwayAround
Indicates that one roadway or route functions as a beltway encircling or surrounding another specified area or location.
-
E.
beltwayType
Indicates the specific classification or type of a beltway (ring road) associated with a given roadway or area.
- 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_69ca848a5a908190aad251f4137b0c3a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b532aa4819087b56be6f5635126 |
completed | April 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd93fc45c8190a823305e461e581d |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:11 p.m.