Triple
T14243629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makhuwa languages |
E353073
|
entity |
| Predicate | hasMember |
P10
|
FINISHED |
| Object | Koti language |
E578696
|
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: Koti language | Statement: [Makhuwa languages, hasMember, Koti language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Koti language Context triple: [Makhuwa languages, hasMember, Koti language]
-
A.
Koti language
chosen
Koti language is a Bantu language spoken primarily along the coast of Mozambique, closely related to other Makua languages.
-
B.
Kati language
The Kati language is a Nuristani language spoken primarily in parts of northeastern Afghanistan and adjacent regions of Pakistan.
-
C.
Kokota language
The Kokota language is an Austronesian language spoken by the Kokota people of Santa Isabel Island in the Solomon Islands.
-
D.
Kurti language
Kurti is an Oceanic Austronesian language spoken in the Admiralty Islands of Papua New Guinea.
-
E.
Pokot language
The Pokot language is a Southern Nilotic language spoken by the Pokot people of Kenya and Uganda.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6245d6a481909ef665748cd4d64c |
completed | April 14, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd28235880819094f5983cce01b0fc |
completed | May 8, 2026, 12:02 a.m. |
Created at: April 10, 2026, 1:08 a.m.