Triple
T16620033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Les Angles ski resort |
E403799
|
entity |
| Predicate | hasSkiInSkiOutAccess |
P123584
|
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: [Les Angles ski resort, hasSkiInSkiOutAccess, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSkiInSkiOutAccess Context triple: [Les Angles ski resort, hasSkiInSkiOutAccess, yes]
-
A.
hasSkiPassSystem
Indicates that there exists a ski pass system associated with or implemented at the referenced entity.
-
B.
hasSkiPass
Indicates that an entity possesses or is assigned a valid ski pass.
-
C.
hasSkiPatrol
Indicates that an entity is served or overseen by a ski patrol responsible for safety and emergency response on the slopes.
-
D.
hasMountainAccess
Indicates that an entity has the right, ability, or means to enter, use, or traverse a mountain area.
-
E.
hasSkiResortType
Indicates that an entity is associated with, or classified by, a specific type or category of ski resort.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3754c934c8190a0a8ddd747681aa7 |
completed | April 18, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7fb02f481908885a226c2191231 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:17 a.m.