Triple

T1597888
Position Surface form Disambiguated ID Type / Status
Subject Central Bohemian Region E34324 entity
Predicate hasHistoricTown P847 FINISHED
Object Kutná Hora E231914 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: Kutná Hora | Statement: [Central Bohemian Region, hasHistoricTown, Kutná Hora]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kutná Hora
Context triple: [Central Bohemian Region, hasHistoricTown, Kutná Hora]
  • A. Kutná Hora chosen
    Kutná Hora is a historic Czech town famed for its medieval silver mines, Gothic architecture, and the macabre Sedlec Ossuary.
  • B. 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.
  • C. Nymburk
    Nymburk is a historic town in the Czech Republic known for its medieval fortifications and location on the Elbe River.
  • D. Kolín
    Kolín is a historic industrial town and important transport hub on the Elbe River in the Central Bohemian Region of the Czech Republic.
  • E. Opava
    Opava is a historic city in the Czech Republic’s Silesian region, known as a former political and cultural center of Silesia.
  • 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_69a885fdcb9c819081ce6f0b8cd477dd completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a9092f5f148190b987bc943e89e29c completed March 5, 2026, 4:40 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae5162c078819085c7fbc11f679d56 completed March 9, 2026, 4:49 a.m.
Created at: March 4, 2026, 7:27 p.m.