Triple

T16112520
Position Surface form Disambiguated ID Type / Status
Subject Southwestern Iran E390913 entity
Predicate language P15 FINISHED
Object Luri E159563 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 | Statement: [Southwestern Iran, language, Luri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Luri
Context triple: [Southwestern Iran, language, Luri]
  • A. Luri chosen
    Luri is a Southwestern Iranian language spoken primarily by the Lur people in western and southwestern Iran.
  • B. Liluah
    Liluah is a suburban locality in the Howrah district of West Bengal, India, known for its residential areas and railway facilities near Kolkata.
  • C. Luro
    Luro is an administrative post and rural area in eastern Timor-Leste known for its mountainous terrain and traditional villages.
  • D. Nomlaki
    Nomlaki are a Native American people of Northern California, traditionally part of the Wintun group and known for their distinct language and cultural practices.
  • E. Lemi
    Lemi is a small rural municipality in southeastern Finland known for its lakes, forests, and traditional Karelian culture.
  • 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_69d87f1a8dd881909f1de6ef78849874 completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e20167ee1481909e56dc632bfc0fc5 completed April 17, 2026, 9:46 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffeba90ffc81909d5eb8f0cfa9f147 completed May 10, 2026, 2:21 a.m.
Created at: April 10, 2026, 5 a.m.