Triple

T12318557
Position Surface form Disambiguated ID Type / Status
Subject Klatovy District E293668 entity
Predicate containsSettlement P847 FINISHED
Object Sušice E299068 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: Sušice | Statement: [Klatovy District, containsSettlement, Sušice]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sušice
Context triple: [Klatovy District, containsSettlement, Sušice]
  • A. Sušice chosen
    Sušice is a town in the Czech Republic known as a local administrative, cultural, and tourist center in the southwestern Plzeň Region.
  • B. Svitavy
    Svitavy is a town in the Czech Republic best known as the birthplace of Oskar Schindler, the industrialist who saved hundreds of Jews during the Holocaust.
  • C. Rumburk
    Rumburk is a small historic town in the northern Czech Republic, near the German border, known for its Baroque architecture and location in the Šluknov Hook region.
  • D. Chomutov
    Chomutov is a city in the northwest of the Czech Republic known for its industrial heritage and location near the Ore Mountains.
  • E. Chotěboř
    Chotěboř is a small historic town in the Czech Republic known for its traditional architecture and location within the Bohemian-Moravian Highlands.
  • 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_69f77f6ed57c8190a365998cd53be873 completed May 3, 2026, 5:01 p.m.
Created at: April 8, 2026, 9:53 p.m.