Triple

T21194820
Position Surface form Disambiguated ID Type / Status
Subject Central Luri E522299 entity
Predicate subdivisionOf P258 FINISHED
Object Luri language 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: Luri language | Statement: [Central Luri, subdivisionOf, Luri language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Luri language
Context triple: [Central Luri, subdivisionOf, 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. Suri language
    The Suri language is a Surmic language spoken by the Suri (Surma) people of southwestern Ethiopia, known for its complex tone system and rich oral tradition.
  • D. Luvale language
    The Luvale language is a Bantu language spoken primarily by the Luvale people of northwestern Zambia and eastern Angola.
  • E. Amarakaeri language
    The Amarakaeri language is an indigenous Harakmbut language spoken by the Amarakaeri people of the Peruvian Amazon.
  • 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_69e0b51061388190aa03f19700d3ef04 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7333aa0fc81909b17eb6a26f389ec completed April 21, 2026, 8:20 a.m.
Created at: April 16, 2026, 3:08 p.m.