Triple

T12595218
Position Surface form Disambiguated ID Type / Status
Subject Chopok E300714 entity
Predicate hasSkiArea P1981 FINISHED
Object Chopok South E300714 NE 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: Chopok South | Statement: [Chopok, hasSkiArea, Chopok South]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chopok South
Context triple: [Chopok, hasSkiArea, Chopok South]
  • A. Chopok chosen
    Chopok is a prominent mountain peak in central Slovakia’s Low Tatras range, popular for hiking, skiing, and panoramic alpine views.
  • B. Chorkówka
    Chorkówka is a village in southeastern Poland known historically as the place where pioneering oil industry chemist and pharmacist Ignacy Łukasiewicz spent his final years and died.
  • C. Olecko
    Olecko is a small town in northeastern Poland known for its lakeside setting and location within the historic region of Masuria.
  • D. Chodzież
    Chodzież is a town in west-central Poland known for its ceramics industry and picturesque lakeside setting.
  • E. Klichaw
    Klichaw is a small town in eastern Belarus known for its rural character and location within the Mogilev Region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d7bdea2ca881908f379526c13b1145 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d954cde3c0819094e74413d6dcf548 completed April 10, 2026, 7:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69f668679dfc8190ac05eeb200f23985 completed May 2, 2026, 9:11 p.m.
Created at: April 9, 2026, 5:08 p.m.