Triple

T6012139
Position Surface form Disambiguated ID Type / Status
Subject Polish–Slovak border E133859 entity
Predicate hasBorderRiver P225 FINISHED
Object Poprad E404653 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: Poprad | Statement: [Polish–Slovak border, hasBorderRiver, Poprad]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Poprad
Context triple: [Polish–Slovak border, hasBorderRiver, Poprad]
  • A. Poprad chosen
    Poprad is a city in northern Slovakia known as a gateway to the High Tatras mountains and an important regional tourism and transport hub.
  • B. Trenčín
    Trenčín is a historic city in western Slovakia known for its medieval castle overlooking the Váh River and its role as a regional cultural and economic center.
  • C. 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.
  • D. Považská Bystrica
    Považská Bystrica is a town in northwestern Slovakia known as an industrial center situated in a valley surrounded by the Strážov Mountains.
  • E. 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.
  • 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_69c0087361a48190905c6b55969852b8 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c04f5159bc8190a988293bbbb99d24 completed March 22, 2026, 8:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69c64b9acb1c8190a51e540371e20bde completed March 27, 2026, 9:19 a.m.
Created at: March 22, 2026, 4:06 p.m.