Triple

T16652946
Position Surface form Disambiguated ID Type / Status
Subject Poprad E404653 entity
Predicate locatedOnRiver P165 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: [Poprad, locatedOnRiver, Poprad River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Poprad River
Context triple: [Poprad, locatedOnRiver, 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_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_6a00bb029fa081909c3e52d09637541a completed May 10, 2026, 5:06 p.m.
Created at: April 10, 2026, 5:18 a.m.