Triple

T12318554
Position Surface form Disambiguated ID Type / Status
Subject Klatovy District E293668 entity
Predicate capital P234 FINISHED
Object Klatovy E296256 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: Klatovy | Statement: [Klatovy District, capital, Klatovy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Klatovy
Context triple: [Klatovy District, capital, Klatovy]
  • A. Klatovy chosen
    Klatovy is a historic town in the Czech Republic known for its well-preserved architecture, including Baroque churches and catacombs, and its role as a regional administrative center.
  • B. Kladruby
    Kladruby is a small town in the Plzeň Region of the Czech Republic, known for its historic Benedictine monastery and picturesque rural setting.
  • C. Rokycany
    Rokycany is a town in the western Czech Republic that serves as an administrative and economic center within the Plzeň Region.
  • D. Ž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.
  • E. Jablunkov
    Jablunkov is a small historic town in the eastern Czech Republic, near the borders with Poland and Slovakia, known for its multicultural Silesian heritage.
  • 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_69d6ab6ae0dc8190b1522a9c1c55c114 completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d93f4ab1b88190979a8403a430a17c completed April 10, 2026, 6:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69f75d78433081909ae0278e9e1abacb completed May 3, 2026, 2:36 p.m.
Created at: April 8, 2026, 9:53 p.m.