Triple
T5792281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lurs |
E128422
|
entity |
| Predicate | language |
P15
|
FINISHED |
| Object | Luri language |
E122577
|
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: Luri language | Statement: [Lurs, language, Luri language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Luri language Context triple: [Lurs, language, Luri language]
-
A.
Luri language
chosen
Luri language is a Southwestern Iranian language spoken primarily by the Lur people in western and southwestern Iran.
-
B.
Nomlaki language
The Nomlaki language is an endangered Native American language traditionally spoken by the Nomlaki people of northern California.
-
C.
Rarámuri language
The Rarámuri language is an indigenous Uto-Aztecan language spoken by the Tarahumara (Rarámuri) people of northern Mexico.
-
D.
Kayeli language
The Kayeli language is an Austronesian language once spoken on Buru Island in Indonesia, now critically endangered or possibly extinct.
-
E.
Murle language
The Murle language is an Eastern Sudanic language spoken primarily by the Murle people of South Sudan.
- 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_69c00845ca68819081a2ce3ecca577f7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a5870b88190bbfaac2782635128 |
completed | March 22, 2026, 5:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c09824c7f0819095565e0f29b3a508 |
completed | March 23, 2026, 1:32 a.m. |
Created at: March 22, 2026, 3:51 p.m.