Triple

T16260154
Position Surface form Disambiguated ID Type / Status
Subject Etosha Pan E394731 entity
Predicate receivesWaterFrom P415 FINISHED
Object Oshigambo River
The Oshigambo River is a seasonal watercourse in northern Namibia that contributes inflow to the Etosha Pan, an expansive salt pan and key feature of Etosha National Park.
E1841990 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: Oshigambo River | Statement: [Etosha Pan, receivesWaterFrom, Oshigambo 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: Oshigambo River
Triple: [Etosha Pan, receivesWaterFrom, Oshigambo River]
Generated description
The Oshigambo River is a seasonal watercourse in northern Namibia that contributes inflow to the Etosha Pan, an expansive salt pan and key feature of Etosha National Park.

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_69d87f221d8081909b0b2063e7528ba2 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e245c3e5388190942b0237ab5d1f0f completed April 17, 2026, 2:37 p.m.
NED1 Entity disambiguation (via context triple) batch_6a24ec0f80a88190aa6f4c69962d7359 completed June 7, 2026, 3:57 a.m.
NEDg Description generation batch_6a24f092aabc81908676a4d355891072 completed June 7, 2026, 4:16 a.m.
NED2 Entity disambiguation (via description) batch_6a24f55704a081908533c0e5d81b1bb2 completed June 7, 2026, 4:36 a.m.
Created at: April 10, 2026, 5:04 a.m.