Triple
T13576424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yakurr people |
E324297
|
entity |
| Predicate | language |
P15
|
FINISHED |
| Object | Lokaa language |
E1005086
|
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: Lokaa language | Statement: [Yakurr people, language, Lokaa language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lokaa language Context triple: [Yakurr people, language, Lokaa language]
-
A.
Lokaa language
chosen
The Lokaa language is a Niger-Congo language spoken primarily by the Lokaa people in and around Ugep in Cross River State, southeastern Nigeria.
-
B.
Loko language
Loko language is a Southern Atlantic language spoken primarily by the Loko people in Sierra Leone.
-
C.
Lokoya language
The Lokoya language is a Nilo-Saharan language spoken by the Lokoya people of South Sudan.
-
D.
Lotuko language
The Lotuko language is an Eastern Nilotic language spoken primarily by the Lotuko people of South Sudan.
-
E.
Löyöp language
The Löyöp language is an Oceanic language spoken by a small community in the Banks Islands of northern Vanuatu.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb02de1988190af2d473973ecd529 |
completed | April 12, 2026, 2:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f76bba21f88190b8952fb0879e623d |
completed | May 3, 2026, 3:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.