Triple

T4875590
Position Surface form Disambiguated ID Type / Status
Subject Tisa River E109194 entity
Predicate tributary P415 FINISHED
Object Körös River E237331 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: Körös River | Statement: [Tisa River, tributary, Körös River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Körös River
Context triple: [Tisa River, tributary, 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. Zala River
    The Zala River is a major river in western Hungary that drains a large catchment area before emptying into Lake Balaton.
  • C. Draga River
    The Draga River is a mountain river in northern Montenegro that flows through the rugged landscapes of Durmitor National Park, contributing to its dramatic canyons and alpine scenery.
  • D. Tisa River
    The Tisa River is a major Central and Eastern European waterway that flows through countries including Ukraine, Romania, Hungary, Slovakia, and Serbia before joining the Danube.
  • E. Cerna River
    The Cerna River is a river in southwestern Romania that flows through the historic spa town of Băile Herculane before joining the Danube.
  • 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_69bd440e9d64819083e82cf33b4d9570 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6dba3efc8190adcf8b30490b4984 completed March 20, 2026, 3:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69be9235e7b8819084fd9eb7c794e0e3 completed March 21, 2026, 12:42 p.m.
Created at: March 20, 2026, 1:27 p.m.