Triple
T24657894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claviere ski area |
E610444
|
entity |
| Predicate | linkedResort |
P51015
|
FINISHED |
| Object | Sauze d'Oulx |
—
|
NE NERFINISHED |
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: Sauze d'Oulx | Statement: [Claviere ski area, linkedResort, Sauze d'Oulx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedResort Context triple: [Claviere ski area, linkedResort, Sauze d'Oulx]
-
A.
associatedResort
chosen
Indicates a relationship where one entity is linked or connected to a specific resort, typically as its related or corresponding resort.
-
B.
isResortOf
Indicates that a location or facility functions as a resort associated with, belonging to, or serving a particular entity (such as a city, region, or organization).
-
C.
combinesResort
Indicates that one entity merges or groups together multiple resort-related entities into a single combined resort context or offering.
-
D.
notableResort
Indicates that a location functions as a resort that is recognized for its significance, prominence, or special reputation.
-
E.
reservationAlsoKnownAs
Indicates that a reservation is referred to by an alternative name or alias.
- 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 2:34 a.m.