Triple

T14347994
Position Surface form Disambiguated ID Type / Status
Subject Yobe River E355777 entity
Predicate hasTributary P415 FINISHED
Object Komadugu Gana River E389030 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: Komadugu Gana River | Statement: [Yobe River, hasTributary, Komadugu Gana River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Komadugu Gana River
Context triple: [Yobe River, hasTributary, Komadugu Gana River]
  • A. Songo River
    The Songo River is a waterway in southwestern Maine that connects Long Lake to Sebago Lake and is known for its scenic, recreational boating route.
  • B. Ngadda River chosen
    The Ngadda River is a waterway in northeastern Nigeria that flows through the city of Maiduguri and contributes to the region’s drainage into Lake Chad.
  • C. Awali River
    The Awali River is a significant watercourse in Lebanon that flows through the region of Sidon before emptying into the Mediterranean Sea.
  • D. Kelwa River
    Kelwa River is a river in Rajasthan, India, that serves as the main water source feeding Rajsamand Lake.
  • E. Assa River
    The Assa River is a mountain river in the North Caucasus that flows through parts of Georgia and Russia before joining the Terek River.
  • 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_69d82790a7e08190877e2d349b2e8d8e completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de8e8d081c8190ac805726a3e98f4c completed April 14, 2026, 6:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffb58e50bc819086622a33b59cc332 completed May 9, 2026, 10:30 p.m.
Created at: April 10, 2026, 1:14 a.m.