Triple
T11167004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pounou |
E264184
|
entity |
| Predicate | relatedGroup |
P37
|
FINISHED |
| Object | Lumbu |
E264180
|
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: Lumbu | Statement: [Pounou, relatedGroup, Lumbu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lumbu Context triple: [Pounou, relatedGroup, Lumbu]
-
A.
Lumbu
chosen
Lumbu is a Bantu ethnic group and language of Central Africa, primarily found in Gabon and the Republic of the Congo, culturally and linguistically related to neighboring Punu people.
-
B.
Negombo
Negombo is a coastal city in western Sri Lanka known historically as a strategic colonial port and today for its fishing industry and beach tourism.
-
C.
Oshikwambi
Oshikwambi is a regional dialect of the Oshiwambo language spoken by the Kwambi people in northern Namibia.
-
D.
Lukula
Lukula is a town located in the Kongo Central Province of the Democratic Republic of the Congo.
-
E.
Nyambo
Nyambo are a Bantu-speaking ethnic group primarily inhabiting Tanzania’s Kagera Region near the western shores of Lake Victoria.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e88843cc81909e503f0921c6d297 |
completed | April 9, 2026, 5:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4aced563c8190a56ab5ff0618d21f |
completed | April 19, 2026, 10:22 a.m. |
Created at: April 8, 2026, 9:29 p.m.