Triple

T16206113
Position Surface form Disambiguated ID Type / Status
Subject Tábor District E393331 entity
Predicate contains P35 FINISHED
Object Soběslav E716886 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: Soběslav | Statement: [Tábor District, contains, Soběslav]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Soběslav
Context triple: [Tábor District, contains, Soběslav]
  • A. Soběslav chosen
    Soběslav is a historic town in the Czech Republic known for its well-preserved medieval center and location in the South Bohemian Region.
  • B. Boleslav
    Boleslav is a masculine given name of Slavic origin, commonly used in Central and Eastern Europe and associated with several historical rulers and nobles.
  • C. Vratislav
    Vratislav is a historical Slavic personal name, borne by several medieval rulers and nobles in Central Europe, particularly in the Czech lands.
  • D. Bretislaus I
    Bretislaus I was an 11th-century Duke of Bohemia known for consolidating Přemyslid power, expanding Bohemian territory, and strengthening the region’s political and ecclesiastical independence within the Holy Roman Empire.
  • E. Vladislav
    Vladislav is a masculine given name of Slavic origin, commonly used in Russia and other Eastern European countries.
  • 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_69d87f1f5bd08190bd01cac0d5b9d2ef completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e2270f047c819084645da27759a3d2 completed April 17, 2026, 12:26 p.m.
NED1 Entity disambiguation (via context triple) batch_6a000ed13b40819096de333872225730 completed May 10, 2026, 4:51 a.m.
Created at: April 10, 2026, 5:03 a.m.