Triple
T22652582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Achomi people |
E559131
|
entity |
| Predicate | ethnonym |
P4709
|
FINISHED |
| Object | Lari |
—
|
NE NERFINISHED |
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: Lari | Statement: [Achomi people, ethnonym, Lari]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lari Context triple: [Achomi people, ethnonym, Lari]
-
A.
Lari
Lari is a regional dialect of the Sindhi language spoken primarily in parts of Sindh, Pakistan.
-
B.
Lari
Lari is a town in Kenya’s Central Region, known for its agricultural activities and its location within Kiambu County.
-
C.
Lari
chosen
The Lari are an Iranian ethnic group traditionally inhabiting parts of southern and southeastern Iran, with communities also present in regions such as Golestan Province.
-
D.
Lai
Lai is a variant spelling of the Chinese surname Li, commonly found in Chinese-speaking communities and their diasporas.
-
E.
Lai
The Lai are an indigenous ethnic group of the broader Mizo community, primarily inhabiting parts of northeast India and neighboring Myanmar, with their own distinct language and cultural traditions.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1703d7d648190aafe275cd04c47cf |
completed | April 29, 2026, 2:43 a.m. |
Created at: April 17, 2026, 3:06 p.m.