Triple

T17045287
Position Surface form Disambiguated ID Type / Status
Subject Levoča E413550 entity
Predicate locatedNear P294 FINISHED
Object Poprad NE NERFINISHED

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: [Levoča, locatedNear, Poprad]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Poprad
Context triple: [Levoča, locatedNear, 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. Dubno
    Dubno is a historic city in western Ukraine known for its medieval castle and role as a regional cultural and economic center.
  • E. 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.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d886cd18288190b006abab23f811b7 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3da9d7e988190a5e3991c7123f9b0 completed April 18, 2026, 7:25 p.m.
Created at: April 10, 2026, 5:33 a.m.