Triple

T20574399
Position Surface form Disambiguated ID Type / Status
Subject Znaim E505176 entity
Predicate hasCzechName P17790 FINISHED
Object Znojmo NE NERFINISHED

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: Znojmo | Statement: [Znaim, hasCzechName, Znojmo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Znojmo
Context triple: [Znaim, hasCzechName, Znojmo]
  • A. Znojmo chosen
    Znojmo is a historic town in the South Moravian Region of the Czech Republic, known for its medieval architecture, wine production, and strategic position near the Austrian border.
  • B. Zlín
    Zlín is a city in the Czech Republic known for its modernist architecture and historical association with the Baťa shoe company.
  • C. Žamberk
    Žamberk is a small historic town in the Pardubice Region of the Czech Republic, known for its picturesque setting in the Orlické Foothills and well-preserved architecture.
  • D. Karviná
    Karviná is an industrial city in the Moravian-Silesian Region of the Czech Republic, historically part of Cieszyn Silesia and known for its coal mining heritage.
  • E. Chrudim
    Chrudim is a historic town in the Pardubice Region of the Czech Republic, known for its well-preserved medieval center and cultural heritage.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4b721588190993ac7b0a9be2736 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a9087af88190a4610ecb29f637ca completed April 20, 2026, 10:30 p.m.
Created at: April 16, 2026, 11:39 a.m.