Triple

T8787645
Position Surface form Disambiguated ID Type / Status
Subject Slovakia and Hungary E209079 entity
Predicate shareMajorBorderCities P85379 FINISHED
Object Komárno–Komárom 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–Komárom | Statement: [Slovakia and Hungary, shareMajorBorderCities, Komárno–Komárom]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Komárno–Komárom
Context triple: [Slovakia and Hungary, shareMajorBorderCities, Komárno–Komárom]
  • 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. Kozármisleny
    Kozármisleny is a small town in southern Hungary, near Pécs, known for its growing residential character and local sports culture.
  • C. Komló
    Komló is a town in southern Hungary known historically for its coal mining and hop-growing industries.
  • D. Šamorín
    Šamorín is a small town in southwestern Slovakia known for its equestrian sports complex, proximity to the Danube River, and growing role as a suburban area near Bratislava.
  • E. Körmend
    Körmend is a small town in western Hungary, known for its historic castle and location near the Austrian border.
  • 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_69ca836168108190bb43d3dc235c1f55 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5f89a84c819085d4cfe4e6dfbda8 completed March 31, 2026, 11:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69cf520678f48190a0af3df75df9b269 completed April 3, 2026, 5:37 a.m.
Created at: March 30, 2026, 6:43 p.m.