Triple

T27328468
Position Surface form Disambiguated ID Type / Status
Subject Kunene River E689723 entity
Predicate languageVariantName P20733 FINISHED
Object Cunene River
The Cunene River is a major river in southwestern Africa that flows from central Angola to the Atlantic Ocean, forming part of the border between Angola and Namibia.
E689723 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: Cunene River | Statement: [Kunene River, languageVariantName, Cunene 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: Cunene River
Triple: [Kunene River, languageVariantName, Cunene River]
Generated description
The Cunene River is a major river in southwestern Africa that flows from central Angola to the Atlantic Ocean, forming part of the border between Angola and Namibia.

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_69ef355d4cb08190ab032c0a2e7d3753 completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69f627ef6bac8190a7edfb950c1ad3c4 completed May 2, 2026, 4:35 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1ccf0b77c48190b66e905f1ddc56d3 completed June 1, 2026, 12:15 a.m.
NEDg Description generation batch_6a1ccf8456c8819096402635e1399ba4 completed June 1, 2026, 12:17 a.m.
NED2 Entity disambiguation (via description) batch_6a2494722c7c8190b67b87014e4a2f0a completed June 6, 2026, 9:43 p.m.
Created at: April 27, 2026, 11:36 a.m.