Triple
T4678165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4 Vallées ski area |
E103731
|
entity |
| Predicate | hasSkiPassSystem |
P58967
|
FINISHED |
| Object | unified 4 Vallées ski pass |
—
|
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: unified 4 Vallées ski pass | Statement: [4 Vallées ski area, hasSkiPassSystem, unified 4 Vallées ski pass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSkiPassSystem Context triple: [4 Vallées ski area, hasSkiPassSystem, unified 4 Vallées ski pass]
-
A.
hasNightSkiing
Indicates that a location or facility offers skiing activities that take place during nighttime under artificial lighting.
-
B.
hasSkiLifts
Indicates that one location or facility is equipped with ski lifts that provide transportation for skiers or visitors.
-
C.
hasSkiLiftType
Indicates the specific type or category of ski lift associated with an entity.
-
D.
hasSkiLiftConnectionTo
Indicates a relationship where one location is directly connected to another by a ski lift, allowing travel between them via that lift.
-
E.
hasSkiLiftConnectionWith
Indicates a relationship where two locations or areas are directly connected by a ski lift that allows travel between them.
- 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_69bd43dda32c8190938b37744ca270fc |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6217e0088190836570522e324dc6 |
completed | March 20, 2026, 3:04 p.m. |
| PDg | Predicate description generation | batch_69bd67c895dc8190ba648002ff54424b |
completed | March 20, 2026, 3:29 p.m. |
Created at: March 20, 2026, 1:16 p.m.