Triple

T11059002
Position Surface form Disambiguated ID Type / Status
Subject Cuando Cubango Province E261454 entity
Predicate hasRiver P165 FINISHED
Object Cubango River E524955 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: Cubango River | Statement: [Cuando Cubango Province, hasRiver, Cubango River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cubango River
Context triple: [Cuando Cubango Province, hasRiver, Cubango River]
  • A. Bodocongó River
    The Bodocongó River is a watercourse in the municipality of Campina Grande, in the state of Paraíba, Brazil.
  • B. Machángara River
    The Machángara River is a waterway in Ecuador that flows through the city of Cuenca, contributing to its urban landscape and local watershed.
  • C. Machángara River
    The Machángara River is a key waterway in Ecuador that flows through and helps drain the metropolitan area of Quito.
  • D. 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.
  • E. Cuito River chosen
    The Cuito River is a significant river in southern Africa that flows through Angola and Namibia, contributing substantially to the Okavango Basin and its inland delta 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_69d6aa98650481908609c7c56bfa7902 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d798a4f3f88190a29710f64cef9d25 completed April 9, 2026, 12:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69e5e890bb9c81908c316a6423e650e6 completed April 20, 2026, 8:49 a.m.
Created at: April 8, 2026, 9:26 p.m.