Triple
T1544514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Ridge Parkway |
E32944
|
entity |
| Predicate | hasSeasonalClosure |
P26586
|
FINISHED |
| Object | winter weather |
—
|
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: winter weather | Statement: [Blue Ridge Parkway, hasSeasonalClosure, winter weather]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeasonalClosure Context triple: [Blue Ridge Parkway, hasSeasonalClosure, winter weather]
-
A.
hasSeasonalStatus
Indicates that an entity’s status, availability, or condition varies according to a particular season or time of year.
-
B.
hasSeasonalPattern
Indicates that the occurrence, intensity, or characteristics of something regularly vary according to a recurring seasonal cycle.
-
C.
openingHoursCharacteristic
Indicates a relationship that specifies particular attributes or features of an entity’s opening hours, such as patterns, exceptions, or special conditions.
-
D.
reopeningDate
Indicates the date on which something that was previously closed is opened again for use or access.
-
E.
hasSeasonType
chosen
Indicates that something is associated with a particular category or type of season (e.g., summer, winter, rainy).
- 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_69a885ed29088190a3c2d5a3d100c16e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa574094048190a2d7fc3ac904d51e |
completed | March 6, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69a907b426dc8190975c024a50955368 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.