Triple

T15912070
Position Surface form Disambiguated ID Type / Status
Subject Olomouc District E385872 entity
Predicate namedAfter P63 FINISHED
Object Olomouc E191130 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: Olomouc | Statement: [Olomouc District, namedAfter, Olomouc]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Olomouc
Context triple: [Olomouc District, namedAfter, Olomouc]
  • A. Olomouc chosen
    Olomouc is a historic city in the eastern Czech Republic known for its well-preserved old town, Baroque architecture, and UNESCO-listed Holy Trinity Column.
  • B. 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.
  • C. Opava
    Opava is a historic city in the Czech Republic’s Silesian region, known as a former political and cultural center of Silesia.
  • D. Hradec Králové
    Hradec Králové is a historic city in the Czech Republic known for its educational institutions, modernist architecture, and role as a regional cultural and economic center.
  • E. Plzeň
    Plzeň is a major city in western Bohemia in the Czech Republic, known for its brewing tradition and industrial 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_69d86da686e4819097cbf3b1fc2d881d completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e156601c988190b9bd0cd75897651b completed April 16, 2026, 9:36 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00179d63688190bda2758ed4b4e4df completed May 10, 2026, 5:29 a.m.
Created at: April 10, 2026, 4:52 a.m.