Triple

T22838661
Position Surface form Disambiguated ID Type / Status
Subject Great Hungarian Plain E566015 entity
Predicate traversedBy P225 FINISHED
Object Körös River 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: Körös River | Statement: [Great Hungarian Plain, traversedBy, Körös River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Körös River
Context triple: [Great Hungarian Plain, traversedBy, Körös River]
  • A. Körös chosen
    Körös is a river in Central Europe that flows through eastern Hungary and parts of Romania before joining the Tisza River.
  • B. Belá River
    The Belá River is a mountain river in northern Slovakia, known for its scenic course through the High Tatras region and popularity for rafting and outdoor recreation.
  • C. Barna River
    The Barna River is a river in the central Indian state of Madhya Pradesh that serves as an important local water source and tributary within the Narmada river basin.
  • D. Sajna River
    The Sajna River is a small river in northern Poland that flows through the town of Reszel in the Warmian-Masurian region.
  • E. Eger River
    The Eger River is a watercourse in Central Europe that flows through parts of Germany and the Czech Republic, serving as a tributary of the Elbe River.
  • 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_69e245869e188190a196584f36e682da completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17e8244dc819089c0a7525fb512ab completed April 29, 2026, 3:44 a.m.
Created at: April 17, 2026, 3:35 p.m.