Triple

T2757694
Position Surface form Disambiguated ID Type / Status
Subject Oldřich Černík E61143 entity
Predicate placeOfBirth P1 FINISHED
Object Ostrava E32147 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: Ostrava | Statement: [Oldřich Černík, placeOfBirth, Ostrava]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ostrava
Context triple: [Oldřich Černík, placeOfBirth, Ostrava]
  • A. Ostrava chosen
    Ostrava is a major industrial and cultural city in the northeastern Czech Republic, near the borders with Poland and Slovakia.
  • B. Opava
    Opava is a historic city in the Czech Republic’s Silesian region, known as a former political and cultural center of Silesia.
  • C. Plzeň
    Plzeň is a major city in western Bohemia in the Czech Republic, known for its brewing tradition and industrial heritage.
  • D. Brno
    Brno is the second-largest city in the Czech Republic, known as a major cultural, educational, and industrial center in the historical region of Moravia.
  • E. Olomouc
    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.
  • 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_69ab4b7a85bc819094a349b84beb1f2c completed March 6, 2026, 9:47 p.m.
NER Named-entity recognition batch_69abdb8ba4688190b401b6eb5b734ac6 completed March 7, 2026, 8:02 a.m.
NED1 Entity disambiguation (via context triple) batch_69b1eed270f881909f907890f5fac412 completed March 11, 2026, 10:38 p.m.
Created at: March 6, 2026, 9:57 p.m.