Triple

T11703711
Position Surface form Disambiguated ID Type / Status
Subject Hurbanovo E278186 entity
Predicate hasNearbyCity P350 FINISHED
Object Komárno E281398 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: Komárno | Statement: [Hurbanovo, hasNearbyCity, Komárno]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Komárno
Context triple: [Hurbanovo, hasNearbyCity, Komárno]
  • A. Komárno chosen
    Komárno is a historic town and river port in southern Slovakia, situated at the confluence of the Danube and Váh rivers on the border with Hungary.
  • B. Kežmarok
    Kežmarok is a historic town in northern Slovakia known for its well-preserved medieval architecture and role as a cultural center of the Spiš (Spisz) region.
  • C. Dunajská Streda
    Dunajská Streda is a town in southern Slovakia known as a cultural and economic center of the Hungarian minority in the country.
  • D. Liptovský Hrádok
    Liptovský Hrádok is a small Slovak town in the Liptov region, known for its historic castle complex and location near the Tatra Mountains.
  • E. Kozármisleny
    Kozármisleny is a small town in southern Hungary, near Pécs, known for its growing residential character and local sports culture.
  • 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_69d6aaff2ce88190b4a1e4b341ad5377 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a49b1080819096593733ee48a187 completed April 10, 2026, 7:19 a.m.
NED1 Entity disambiguation (via context triple) batch_69f417302ffc81908d222c4e01fa3e95 completed May 1, 2026, 3 a.m.
Created at: April 8, 2026, 9:40 p.m.