Triple

T6964741
Position Surface form Disambiguated ID Type / Status
Subject Silesian Lachs E161459 entity
Predicate culturalRegion P1968 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: [Silesian Lachs, culturalRegion, Cieszyn Silesia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cieszyn Silesia
Context triple: [Silesian Lachs, culturalRegion, 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_69c68853cff881908439d488924a8283 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6daf2b7bc8190a3e73f3b24f0352b completed March 27, 2026, 7:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1bc96f7288190ab8d1bbf9d428903 completed April 5, 2026, 1:36 a.m.
Created at: March 27, 2026, 2:30 p.m.