Triple
T27745526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Col du Mollendruz |
E701971
|
entity |
| Predicate | isAllSeasonAccess |
P8056
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Col du Mollendruz, isAllSeasonAccess, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAllSeasonAccess Context triple: [Col du Mollendruz, isAllSeasonAccess, yes]
-
A.
hasSeasonalStatus
Indicates that an entity’s status, availability, or condition varies according to a particular season or time of year.
-
B.
isUsedAllYear
chosen
Indicates that something is utilized or remains in active use throughout the entire year, without being limited to a particular season or period.
-
C.
hasSeasonType
Indicates that something is associated with a particular category or type of season (e.g., summer, winter, rainy).
-
D.
hasSeasonalParticipationIn
Indicates that an entity takes part in or is involved with another entity only during specific seasons or recurring seasonal periods.
-
E.
hasUseSeason
Indicates the season or time of year during which something is intended or suitable to be used.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 4:15 p.m.