Triple
T22827826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Furka Oberalp Railway |
E565707
|
entity |
| Predicate | seasonalConstraints |
P15928
|
FINISHED |
| Object | heavy winter snow |
—
|
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: heavy winter snow | Statement: [Furka Oberalp Railway, seasonalConstraints, heavy winter snow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonalConstraints Context triple: [Furka Oberalp Railway, seasonalConstraints, heavy winter snow]
-
A.
seasonalValidity
Indicates that something is valid, applicable, or in effect only during a specific season or set of seasons.
-
B.
basedOnSeason
Indicates that something is determined, influenced, or derived according to a particular season or time of year.
-
C.
hasSeasonalStatus
chosen
Indicates that an entity’s status, availability, or condition varies according to a particular season or time of year.
-
D.
isSeasonalStandard
Indicates that something follows or conforms to the standard conditions, rules, or patterns that apply only during a specific season or time period.
-
E.
requiresSameSeason
Indicates that the related entities must occur, be available, or be used within the same season.
- 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_69e24585ab1c81909b2b5065d15805d5 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e2914188190be6cdbd8167cd806 |
completed | April 29, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:34 p.m.