Triple

T22140034
Position Surface form Disambiguated ID Type / Status
Subject Podolínec E547132 entity
Predicate locatedOn P40 FINISHED
Object Poprad River E24618 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 River | Statement: [Podolínec, locatedOn, Poprad River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Poprad River
Context triple: [Podolínec, locatedOn, Poprad River]
  • A. Poprad River chosen
    The Poprad River is a mountain river in southern Poland and northeastern Slovakia, known for its scenic valley, spa towns, and role as part of the Polish-Slovak border.
  • B. Bystrica River
    The Bystrica River is a Slovak river that flows through central Slovakia and joins the Hron River as one of its notable tributaries.
  • C. Bystritsa River
    The Bystritsa River is a significant watercourse in Russia that serves as one of the main tributaries feeding the Vyatka River system.
  • D. Turiec River
    The Turiec River is a significant river in north-central Slovakia that flows through the Turiec Basin before joining the Váh River.
  • E. Opava River
    The Opava River is a significant watercourse in the Czech Republic that flows through the historical region of Silesia, including the city of Opava, before joining the Oder River.
  • 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_69e11e3a95d88190a3bd80d9471976c3 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f129bda1208190b851ae5c68b760e9 completed April 28, 2026, 9:42 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0a96fa6fc08190b2985b2b350c7336 completed May 18, 2026, 4:35 a.m.
Created at: April 16, 2026, 8:32 p.m.