Triple

T15016958
Position Surface form Disambiguated ID Type / Status
Subject Faraya–Mzaar ski area E377980 entity
Predicate hasApproximateNumberOfRuns P116400 FINISHED
Object more than 40 ski runs 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: more than 40 ski runs | Statement: [Faraya–Mzaar ski area, hasApproximateNumberOfRuns, more than 40 ski runs]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasApproximateNumberOfRuns
Context triple: [Faraya–Mzaar ski area, hasApproximateNumberOfRuns, more than 40 ski runs]
  • A. hasApproximateStepCount
    Indicates that an entity is associated with an estimated or non-exact number of steps.
  • B. hasApproximateRate
    Indicates that one entity is associated with another entity representing an estimated or non-exact rate or frequency.
  • C. runsApproximately
    Indicates that an entity performs a running action in a manner that is close to, but not exactly matching, a specified time, distance, speed, or other running-related measure.
  • D. hasApproximateDuration
    Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
  • E. numberOfExecutions
    Indicates the count of times a particular action, process, or event has been carried out.
  • 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_69d85cd3a3c881908c71fc424d459c17 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded7633fcc8190b2231f43252bc46f completed April 15, 2026, 12:10 a.m.
PD Predicate disambiguation batch_69de9a67cbc481909c19c2de57de4eb7 completed April 14, 2026, 7:50 p.m.
PDg Predicate description generation batch_69deb1a88d588190996afa8e5b32b552 completed April 14, 2026, 9:29 p.m.
Created at: April 10, 2026, 2:55 a.m.