Triple
T16958336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ijoid |
E411361
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Defaka language |
E407517
|
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: Defaka language | Statement: [Ijoid, hasPart, Defaka language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Defaka language Context triple: [Ijoid, hasPart, Defaka language]
-
A.
Defaka language
chosen
The Defaka language is a highly endangered Niger-Congo language spoken by a small community in Nigeria’s Niger Delta region.
-
B.
Daakaka language
The Daakaka language is an Oceanic language spoken by communities on Ambrym Island in Vanuatu.
-
C.
Damara language
The Damara language is a Khoe (Central Khoisan) language spoken primarily by the Damara people of Namibia.
-
D.
Hoanya language
The Hoanya language is an extinct Austronesian language once spoken by the Hoanya people of western Taiwan and classified among the indigenous Formosan languages.
-
E.
Bafia language
The Bafia language is a Bantu language spoken primarily by the Bafia people in central Cameroon.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d01d34d08190a73ce48e9988bd97 |
completed | April 18, 2026, 6:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00d468f5048190aa43b212ec7a7306 |
completed | May 10, 2026, 6:54 p.m. |
Created at: April 10, 2026, 5:31 a.m.