Triple
T2807939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salang Pass |
E54097
|
entity |
| Predicate | seasonalRestriction |
P15928
|
FINISHED |
| Object | occasional winter closures |
—
|
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: occasional winter closures | Statement: [Salang Pass, seasonalRestriction, occasional winter closures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonalRestriction Context triple: [Salang Pass, seasonalRestriction, occasional winter closures]
-
A.
hasSeasonalStatus
chosen
Indicates that an entity’s status, availability, or condition varies according to a particular season or time of year.
-
B.
hasSeasonalHighlight
Indicates that something features a notable or emphasized aspect during a particular season or time of year.
-
C.
affectedSeason
Indicates that one entity has an influence on, or causes a change in, a particular season.
-
D.
hasSeasonalEvents
Indicates that an entity organizes or experiences events that occur only during specific seasons or times of the year.
-
E.
hasSeasonalNature
Indicates that something exhibits characteristics, behavior, or occurrence patterns that vary according to specific seasons or times of the year.
- 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_69ab49dcee188190b5c6eca9ae9e3469 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde2fdcf88190a52e515c166ea8f7 |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd059f308190853191f6ffe2bc6f |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.