Triple

T10798849
Position Surface form Disambiguated ID Type / Status
Subject Náchod District E254783 entity
Predicate hasRiver P165 FINISHED
Object Úpa River E339098 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: Úpa River | Statement: [Náchod District, hasRiver, Úpa River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Úpa River
Context triple: [Náchod District, hasRiver, Úpa River]
  • A. Úpa River chosen
    The Úpa River is a river in the northeastern Czech Republic that flows from the Krkonoše (Giant) Mountains through towns such as Trutnov before joining the Labe (Elbe) River.
  • B. Umiam River
    Umiam River is a river in the Indian state of Meghalaya that feeds the scenic Umiam Lake near Shillong and supports regional hydropower and water resources.
  • C. Adaja River
    The Adaja River is a significant river in central Spain that flows through the province of Ávila before joining the Douro River system.
  • D. Letaba River
    The Letaba River is a major watercourse in northeastern South Africa that flows through the Kruger National Park, supporting diverse wildlife and ecosystems along its banks.
  • E. Bandia River
    The Bandia River is a lesser-known river in India that serves as a tributary of the Indravati River within the Godavari basin.
  • 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_69d6aa61c15c8190a1839550c56e75e1 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d73334feb08190aae967eaa37659f7 completed April 9, 2026, 5:03 a.m.
NED1 Entity disambiguation (via context triple) batch_69f78ac420788190b12167aef7436c64 completed May 3, 2026, 5:49 p.m.
Created at: April 8, 2026, 9:17 p.m.