Triple

T16816621
Position Surface form Disambiguated ID Type / Status
Subject Lunga River E408767 entity
Predicate hasMouthIn P1008 FINISHED
Object Kafue 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: Kafue River | Statement: [Lunga River, hasMouthIn, Kafue River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kafue River
Context triple: [Lunga River, hasMouthIn, Kafue River]
  • A. Kafue River chosen
    The Kafue River is one of Zambia’s major rivers, flowing through the Kafue Flats and Kafue National Park before joining the Zambezi and supporting significant hydropower, agriculture, and wildlife habitats.
  • B. Zambezi River
    The Zambezi River is one of Africa’s largest rivers, famed for Victoria Falls and its role as a vital waterway and natural border in southern Africa.
  • C. Lusaka River
    The Lusaka River is a watercourse in Zambia that gave its name to the nation’s capital city, Lusaka.
  • D. Kunda River
    Kunda River is a regional river flowing through the Khargone district in the Indian state of Madhya Pradesh.
  • E. Kunda River
    Kunda River is a tributary watercourse in Russia that feeds into the Unzha River within the Volga basin.
  • 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_69d88394566c8190b3dcbdc72935f7fa completed April 10, 2026, 4:59 a.m.
NER Named-entity recognition batch_69e3b2e1de908190aa3508770fb865cf completed April 18, 2026, 4:35 p.m.
Created at: April 10, 2026, 5:23 a.m.