Triple

T8760730
Position Surface form Disambiguated ID Type / Status
Subject Karviná E208190 entity
Predicate locatedIn P40 FINISHED
Object Cieszyn Silesia E31409 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: Cieszyn Silesia | Statement: [Karviná, locatedIn, Cieszyn Silesia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cieszyn Silesia
Context triple: [Karviná, locatedIn, Cieszyn Silesia]
  • A. Cieszyn Silesia chosen
    Cieszyn Silesia is a historical and ethnically diverse borderland region centered around the city of Cieszyn, spanning areas of present-day Poland and the Czech Republic.
  • B. Cieszyn
    Cieszyn is a historic town in southern Poland on the Olza River, known for its shared Polish-Czech heritage and well-preserved old town.
  • C. Katowice
    Katowice is a major industrial and cultural city in southern Poland, known as the capital of the Silesian region.
  • D. Chorzów
    Chorzów is an industrial city in southern Poland’s Silesian region, known for its heavy industry heritage and the extensive Silesian Park.
  • E. Opole Silesia
    Opole Silesia is a historical and cultural region in southwestern Poland, known for its mixed Polish-German heritage and centered around the city of Opole.
  • 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_69ca835df7e08190ac875664cca8f9ca completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5df9729481908679151988b76d2f completed March 31, 2026, 11:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69f018324bf88190bcd2bf168b1065d3 completed April 28, 2026, 2:15 a.m.
Created at: March 30, 2026, 6:40 p.m.