Triple

T22290201
Position Surface form Disambiguated ID Type / Status
Subject Vysoké Tatry E550973 entity
Predicate contains P35 FINISHED
Object Podbanské 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: Podbanské | Statement: [Vysoké Tatry, contains, Podbanské]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Podbanské
Context triple: [Vysoké Tatry, contains, Podbanské]
  • A. Podbanské chosen
    Podbanské is a small mountain resort settlement in northern Slovakia, situated in the High Tatras near the Belá River.
  • B. Pálava
    Pálava is a renowned wine-producing region in the Czech Republic, noted for its limestone hills and high-quality white wines, especially aromatic varieties.
  • C. Bobrůvka
    Bobrůvka is a river in the Czech Republic that flows through the Vysočina and South Moravian regions before joining the Svratka River.
  • D. Blansko
    Blansko is a small industrial town in the South Moravian Region of the Czech Republic, known as a gateway to the Moravian Karst cave system.
  • E. Poltár
    Poltár is a small town in central Slovakia known historically for its glassmaking industry and location within the Banská Bystrica administrative region.
  • 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_69e11e45fb848190a1b2ae21296e3a5f completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f1560adde88190961d8fc24c1c4b3c completed April 29, 2026, 12:51 a.m.
Created at: April 16, 2026, 8:41 p.m.