Triple
T31790010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linn Cove Visitor Center |
E811436
|
entity |
| Predicate | roadMilepost |
P89390
|
FINISHED |
| Object | Blue Ridge Parkway milepost 304.4 |
—
|
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: Blue Ridge Parkway milepost 304.4 | Statement: [Linn Cove Visitor Center, roadMilepost, Blue Ridge Parkway milepost 304.4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadMilepost Context triple: [Linn Cove Visitor Center, roadMilepost, Blue Ridge Parkway milepost 304.4]
-
A.
riverMilepost
Indicates the specific distance or position along a river, measured in miles from a defined starting point.
-
B.
nearbyHighwayMilepost
Indicates that one entity is located close to a specific highway milepost associated with another entity.
-
C.
trailMilepostOn
Indicates that a specific milepost is physically located on and associated with a particular trail segment or trail route.
-
D.
blueRidgeParkwayMilepost
chosen
Indicates a specific location or reference point identified by its milepost number along the Blue Ridge Parkway.
-
E.
approximateMileMarker
Indicates an estimated or not precisely measured position along a route expressed in miles.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ac186f888190979084647ec49b6a |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa21f2508190a204a424ffc00ca6 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:38 p.m.