Triple

T15618752
Position Surface form Disambiguated ID Type / Status
Subject Sangha River E375487 entity
Predicate hasTributary P415 FINISHED
Object Ngoko River
The Ngoko River is a significant waterway in Central Africa that forms part of the Sangha River basin and contributes to the Congo River system.
E1750962 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: Ngoko River | Statement: [Sangha River, hasTributary, Ngoko River]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Ngoko River
Triple: [Sangha River, hasTributary, Ngoko River]
Generated description
The Ngoko River is a significant waterway in Central Africa that forms part of the Sangha River basin and contributes to the Congo River system.

Provenance (5 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_69d85ccf2794819096cda4cbcb02d478 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04e997ce481909b2f10d25705fbc6 completed April 16, 2026, 2:51 a.m.
NED1 Entity disambiguation (via context triple) batch_6a1229647ffc8190bb1520998a400419 completed May 23, 2026, 10:25 p.m.
NEDg Description generation batch_6a122ad103b08190b8eddc14442802f6 completed May 23, 2026, 10:31 p.m.
NED2 Entity disambiguation (via description) batch_6a122b4b3c488190b95edec5469dfd71 completed May 23, 2026, 10:33 p.m.
Created at: April 10, 2026, 4:13 a.m.