Triple
T2533996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic–Congo languages |
E56225
|
entity |
| Predicate | includesLanguage |
P2177
|
FINISHED |
| Object | Oshiwambo |
E99877
|
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: Oshiwambo | Statement: [Atlantic–Congo languages, includesLanguage, Oshiwambo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oshiwambo Context triple: [Atlantic–Congo languages, includesLanguage, Oshiwambo]
-
A.
Oshiwambo
chosen
Oshiwambo is a Bantu language (or cluster of closely related dialects) widely spoken by the Ovambo people in northern Namibia and southern Angola.
-
B.
Asago
Asago is a city in northern Hyōgo Prefecture, Japan, known for its mountainous scenery, historic castle ruins, and hot spring resorts.
-
C.
Nakanamanga
Nakanamanga is an Oceanic Austronesian language spoken primarily on Efate Island and nearby areas in Vanuatu.
-
D.
Isanzu
Isanzu is a Bantu language spoken by the Isanzu people of north-central Tanzania.
-
E.
Awaba
Awaba is an Aboriginal name historically used for Lake Macquarie, a large coastal lake in New South Wales, Australia.
- 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_69ab4a49b6508190bc467fbef4bac334 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd27afe7c8190984e10d3f3d5586b |
completed | March 7, 2026, 7:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af5cf858cc81908d6a7ef5315119aa |
completed | March 9, 2026, 11:51 p.m. |
Created at: March 6, 2026, 9:47 p.m.