Triple
T17193496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mende language |
E417285
|
entity |
| Predicate | closelyRelatedTo |
P37
|
FINISHED |
| Object | Loma language |
E996638
|
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: Loma language | Statement: [Mende language, closelyRelatedTo, Loma language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Loma language Context triple: [Mende language, closelyRelatedTo, Loma language]
-
A.
Lolo language
The Lolo language is a Bantu language of the Makhuwa group spoken by communities in northern Mozambique.
-
B.
Nomlaki language
The Nomlaki language is an endangered Native American language traditionally spoken by the Nomlaki people of northern California.
-
C.
Loko language
chosen
Loko language is a Southern Atlantic language spoken primarily by the Loko people in Sierra Leone.
-
D.
Huambisa language
The Huambisa language is an indigenous Jivaroan language spoken by the Huambisa (Wampis) people of the northern Peruvian Amazon.
-
E.
Curripaco language
The Curripaco language is an Arawakan language spoken by the Curripaco people of the Northwest Amazon region in Brazil, Colombia, and Venezuela.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42da93bf88190b60b658087779d36 |
completed | April 19, 2026, 1:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a015fd393ac8190afc4c076b6cf60ba |
completed | May 11, 2026, 4:49 a.m. |
Created at: April 10, 2026, 5:38 a.m.