Triple

T12742706
Position Surface form Disambiguated ID Type / Status
Subject Gorals E304526 entity
Predicate traditionalRegion P1968 FINISHED
Object Żywiec Beskids E427375 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: Żywiec Beskids | Statement: [Gorals, traditionalRegion, Żywiec Beskids]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Żywiec Beskids
Context triple: [Gorals, traditionalRegion, Żywiec Beskids]
  • A. Żywiec Beskids chosen
    Żywiec Beskids is a mountain range in southern Poland known for its high peaks, including Babia Góra, and popular hiking and skiing areas.
  • B. Sucha Beskidzka
    Sucha Beskidzka is a small historic town in southern Poland, known for its picturesque Beskid mountain setting and its Renaissance-style castle.
  • 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. Bukowina Tatrzańska
    Bukowina Tatrzańska is a popular mountain village and tourist resort in southern Poland, known for its traditional Highlander culture, ski facilities, and thermal baths.
  • 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_69d7bdf1426c8190a4402e1c4cdec33a completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96bd321bc81908eb61cc05b550754 completed April 10, 2026, 9:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69f67c91ed7c81909165dc300d5b23ae completed May 2, 2026, 10:37 p.m.
Created at: April 9, 2026, 5:26 p.m.