Triple

T21808513
Position Surface form Disambiguated ID Type / Status
Subject Lochkov E538410 entity
Predicate locatedNear P294 FINISHED
Object Radotín NE NERFINISHED

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: Radotín | Statement: [Lochkov, locatedNear, Radotín]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Radotín
Context triple: [Lochkov, locatedNear, Radotín]
  • A. Radotín chosen
    Radotín is a district in the southwestern part of Prague, Czech Republic, known for its location in the Berounka River valley and its mix of residential areas and natural surroundings.
  • B. Hněvotín
    Hněvotín is a small municipality and village in the Olomouc Region of the Czech Republic, located near the city of Olomouc.
  • C. Husinec
    Husinec is a small Czech town best known as the birthplace of the religious reformer Jan Hus.
  • D. Moravice
    Moravice is a river in the northern part of the historical Moravia region of the Czech Republic.
  • E. Fryštát
    Fryštát is a historic town in the Czech Republic, now part of Karviná, known for its medieval origins and former status as a key settlement in the Duchy of Teschen.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c473f0f8819086c9d1b4a143bd67 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f078047ca88190a0efa4bc7f2faf80 completed April 28, 2026, 9:04 a.m.
Created at: April 16, 2026, 6:53 p.m.