Triple
T14288385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Plagne |
E354237
|
entity |
| Predicate | liftSystem |
P59567
|
FINISHED |
| Object | chairlifts |
—
|
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: chairlifts | Statement: [La Plagne, liftSystem, chairlifts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liftSystem Context triple: [La Plagne, liftSystem, chairlifts]
-
A.
hasLiftOrLaunchSystem
Indicates that an entity is equipped with, or associated with, a system used to lift, launch, or otherwise deploy another object or vehicle.
-
B.
hasLift
Indicates that one entity is equipped with, contains, or provides access to a lift (elevator).
-
C.
landingGear
Indicates that an entity’s landing gear is present, deployed, or otherwise involved in a landing-related state or action relative to another entity or context.
-
D.
cableCarSystem
chosen
Indicates a relationship where a transportation system operates vehicles pulled by cables along fixed routes, typically on steep gradients.
-
E.
hasWinchCapacity
Indicates that an entity is equipped with a winch capable of exerting or handling a specified load or pulling capacity.
- 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de698023288190b1d705235c2b2ca3 |
completed | April 14, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:11 a.m.