Triple
T4049026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clingmans Dome |
E84137
|
entity |
| Predicate | seasonalRoadClosure |
P10162
|
FINISHED |
| Object | Clingmans Dome Road closed in winter |
—
|
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: Clingmans Dome Road closed in winter | Statement: [Clingmans Dome, seasonalRoadClosure, Clingmans Dome Road closed in winter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonalRoadClosure Context triple: [Clingmans Dome, seasonalRoadClosure, Clingmans Dome Road closed in winter]
-
A.
roadAccessSeason
chosen
Indicates the time of year or season during which road access to a place or area is available or permitted.
-
B.
isRoadAccessible
Indicates that a road can be safely and legally used or traversed under the current conditions.
-
C.
roadTraffic
Indicates the presence, flow, or conditions of vehicles and movement along roads or streets.
-
D.
closedToThroughTraffic
Indicates that a route or area is not accessible for general passage and cannot be used as a through route for traffic.
-
E.
roadTraverses
Indicates that a road passes through, crosses, or extends across a specified geographic area or feature.
- 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_69aed930bd5c819083e7dcc14fc44f69 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb82d1a08190aa8c5c48d368b58b |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef900386481909d04555a9ec9b0e3 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:37 p.m.