Triple

T13267338
Position Surface form Disambiguated ID Type / Status
Subject Topľa E315955 entity
Predicate flowsInto P408 FINISHED
Object Ondava River E1250325 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: Ondava River | Statement: [Topľa, flowsInto, Ondava River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ondava River
Context triple: [Topľa, flowsInto, Ondava River]
  • A. Ondava River chosen
    The Ondava River is a river in eastern Slovakia that flows through the Zemplín region and contributes to the Bodrog River system.
  • B. Lovat River
    The Lovat River is a waterway in northwestern Russia that flows through the Novgorod region before emptying into Lake Ilmen.
  • C. Jonte River
    The Jonte River is a scenic watercourse in southern France that flows through the dramatic limestone landscapes and gorges of the Grands Causses region.
  • D. Kandia River
    The Kandia River is a mountain river in northern Pakistan that flows through the remote Kandia Valley in the Kohistan region before joining the Indus River.
  • E. Obikhingou River
    The Obikhingou River is a mountain river in Tajikistan that flows through the Pamir-Alay ranges and contributes significantly to the Vakhsh River system.
  • 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_69d806b1d9ac8190852c5571d5bd5f0f completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d9901e44bc8190966f87ae219d6bf4 completed April 11, 2026, 12:04 a.m.
NED1 Entity disambiguation (via context triple) batch_6a014132570081909fab220c002c2f10 completed May 11, 2026, 2:38 a.m.
Created at: April 9, 2026, 9:25 p.m.