Triple

T10273857
Position Surface form Disambiguated ID Type / Status
Subject Košice Region E240912 entity
Predicate containsCity P294 FINISHED
Object Trebišov E291276 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: Trebišov | Statement: [Košice Region, containsCity, Trebišov]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Trebišov
Context triple: [Košice Region, containsCity, Trebišov]
  • A. Trebišov chosen
    Trebišov is a town in eastern Slovakia known as an administrative and cultural center of the Trebišov District.
  • B. Levoča
    Levoča is a historic town in eastern Slovakia renowned for its well-preserved medieval center and Gothic architecture, including the Church of St. James with its famous wooden altar by Master Paul.
  • C. Ružomberok
    Ružomberok is a town in northern Slovakia known for its location in the Liptov region and its historical and cultural significance.
  • D. Tišnov
    Tišnov is a small historic town in the South Moravian Region of the Czech Republic, located northwest of Brno.
  • E. Prešporok
    Prešporok is the historical Slovak name for the city now known as Bratislava, the capital of Slovakia.
  • 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_69d381a94c1881908fc38fc263d9b9c2 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d288acf48190bbf14a5cb2dfe1f4 completed April 7, 2026, 9:46 a.m.
NED1 Entity disambiguation (via context triple) batch_69d998671c1c8190be2012a3faf6ba35 completed April 11, 2026, 12:40 a.m.
Created at: April 6, 2026, 11:36 a.m.