Triple
T20114171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oeschinen Lake |
E490409
|
entity |
| Predicate | summerTouristSeason |
P138738
|
FINISHED |
| Object | June to September |
—
|
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: June to September | Statement: [Oeschinen Lake, summerTouristSeason, June to September]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summerTouristSeason Context triple: [Oeschinen Lake, summerTouristSeason, June to September]
-
A.
summerPeak
Indicates that something reaches its highest level, intensity, or activity during the summer season.
-
B.
summerAccess
Indicates that an entity is permitted to use or enter a resource, place, or service specifically during the summer period.
-
C.
summerHomeOf
Indicates that a location serves as a seasonal or vacation residence for a person or group, specifically used during the summer.
-
D.
summerBase
Indicates a base or location where an entity is situated or operates specifically during the summer season.
-
E.
summerPhase
Indicates the specific stage or period within the summer season that an entity is in or associated with.
- F. None of above. chosen
Provenance (4 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666e31af081908d8e0c867c388a73 |
completed | April 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc2bc3c819088c33cd263303433 |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:29 p.m.