Triple
T18619800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parsenn ski area |
E455116
|
entity |
| Predicate | hasRun |
P132427
|
FINISHED |
| Object | Parsenn descent to Küblis |
—
|
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: Parsenn descent to Küblis | Statement: [Parsenn ski area, hasRun, Parsenn descent to Küblis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRun Context triple: [Parsenn ski area, hasRun, Parsenn descent to Küblis]
-
A.
hasRunType
Indicates the type or category of a run associated with an entity (e.g., execution mode, run classification, or run configuration).
-
B.
hasCompleted
Indicates that an entity has finished or successfully carried out a specified task, process, or activity.
-
C.
hasMet
Indicates that one entity has encountered or come into contact with another entity at least once.
-
D.
hasBuilt
Indicates that one entity is the creator or constructor of another entity.
-
E.
hasLaunchedFor
Indicates that an entity (such as a product, feature, or service) has been officially released or made available specifically for another entity (such as a user, group, market, or platform).
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54f00889c8190931f8d3fbabd531b |
completed | April 19, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e485f5d1588190b44f31cbc54c0a9d |
completed | April 19, 2026, 7:36 a.m. |
Created at: April 10, 2026, 11:46 a.m.