Triple
T17629604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Grave |
E429938
|
entity |
| Predicate | skiAreaCharacter |
P35252
|
FINISHED |
| Object | unpatrolled off-piste terrain |
—
|
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: unpatrolled off-piste terrain | Statement: [La Grave, skiAreaCharacter, unpatrolled off-piste terrain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skiAreaCharacter Context triple: [La Grave, skiAreaCharacter, unpatrolled off-piste terrain]
-
A.
skiAreaName
Indicates that an entity has a specific name used to identify a ski area.
-
B.
skiAreaType
chosen
Indicates the specific type or classification of a ski area associated with an entity (e.g., resort, backcountry, terrain park).
-
C.
touristCharacter
Indicates that an entity has the role, behavior, or qualities characteristic of a tourist in relation to another entity or context.
-
D.
skiAreaLinkedTo
Indicates that one ski area is connected or associated with another, such as through shared lifts, trails, passes, or coordinated operations.
-
E.
skiAreaServedBy
Indicates that a ski area is provided with services, access, or support by a specified entity (such as a company, organization, or facility).
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46dbf59dc8190a56aa4a2449b2e2e |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:52 a.m.