Triple

T16652963
Position Surface form Disambiguated ID Type / Status
Subject Poprad E404653 entity
Predicate railConnectionTo P13914 FINISHED
Object Košice E47856 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: Košice | Statement: [Poprad, railConnectionTo, Košice]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Košice
Context triple: [Poprad, railConnectionTo, Košice]
  • A. Košice chosen
    Košice is a major city in eastern Slovakia known for its historic Old Town, Gothic St. Elisabeth Cathedral, and role as an important cultural and economic center.
  • B. Banská Bystrica
    Banská Bystrica is a historic central Slovak city best known as the main center of the anti-Nazi Slovak National Uprising during World War II.
  • C. 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.
  • D. Bratislava
    Bratislava is the capital and largest city of Slovakia, situated along the Danube River near the borders with Austria and Hungary.
  • E. Prešov
    Prešov is a historic city in eastern Slovakia known for its preserved medieval center and role as a regional cultural and economic hub.
  • 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_69d8838b5fbc81908c6575c132b82e80 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e37bf861348190b2b0b5574d4ddb4f completed April 18, 2026, 12:41 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0084c4c6a08190874264b2840fc70d completed May 10, 2026, 1:14 p.m.
Created at: April 10, 2026, 5:18 a.m.