Triple

T11795987
Position Surface form Disambiguated ID Type / Status
Subject Nitra Region E280506 entity
Predicate hasCity P316 FINISHED
Object Hurbanovo E278186 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: Hurbanovo | Statement: [Nitra Region, hasCity, Hurbanovo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hurbanovo
Context triple: [Nitra Region, hasCity, Hurbanovo]
  • A. Hurbanovo chosen
    Hurbanovo is a small town in southern Slovakia known for its warm climate and its major brewery, Zlatý Bažant.
  • B. Husinec
    Husinec is a small Czech town best known as the birthplace of the religious reformer Jan Hus.
  • C. Nové Hrady
    Nové Hrady is a historic town in the Czech Republic known for its well-preserved castle and location near the Austrian border in the South Bohemian Region.
  • D. Hronov
    Hronov is a small town in the Hradec Králové Region of the Czech Republic, known as the birthplace of writer Alois Jirásek and for its traditional cultural events.
  • E. Osek
    Osek is a town in the Czech Republic historically associated with the family origins of writer Franz Kafka’s father, Hermann Kafka.
  • 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_69d6ab258b808190b1735835c841e3a4 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8a5a1cda0819092d66a82fd882786 completed April 10, 2026, 7:24 a.m.
NED1 Entity disambiguation (via context triple) batch_69f130fd7b9881909e79ecb49fe98d30 completed April 28, 2026, 10:13 p.m.
Created at: April 8, 2026, 9:42 p.m.