Triple

T16360117
Position Surface form Disambiguated ID Type / Status
Subject Podtatrze region E397286 entity
Predicate hasMajorTown P316 FINISHED
Object Sucha Beskidzka E11393 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: Sucha Beskidzka | Statement: [Podtatrze region, hasMajorTown, Sucha Beskidzka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sucha Beskidzka
Context triple: [Podtatrze region, hasMajorTown, Sucha Beskidzka]
  • A. Sucha Beskidzka chosen
    Sucha Beskidzka is a small historic town in southern Poland, known for its picturesque Beskid mountain setting and its Renaissance-style castle.
  • B. Żywiec Beskids
    Żywiec Beskids is a mountain range in southern Poland known for its high peaks, including Babia Góra, and popular hiking and skiing areas.
  • C. Maków Beskids
    Maków Beskids is a mountain range in the Western Beskids of southern Poland, known for its rolling forested hills and small towns.
  • D. Monowice
    Monowice is a village in southern Poland that became historically significant as the site of the Nazi German Auschwitz III-Monowitz labor camp during World War II.
  • E. Bystra Śląska
    Bystra Śląska is a village in southern Poland, located in the Silesian Beskids near Bielsko-Biała.
  • 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_69d87f2778dc8190aa95c7572db127e6 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e2fad241848190a9f32c7b050f20a5 completed April 18, 2026, 3:30 a.m.
NED1 Entity disambiguation (via context triple) batch_6a002dbce2508190b655de87f48e841e completed May 10, 2026, 7:03 a.m.
Created at: April 10, 2026, 5:07 a.m.