Triple

T16300394
Position Surface form Disambiguated ID Type / Status
Subject Mazanderani E395767 entity
Predicate closelyRelatedTo P37 FINISHED
Object Gilaki E77850 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: Gilaki | Statement: [Mazanderani, closelyRelatedTo, Gilaki]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gilaki
Context triple: [Mazanderani, closelyRelatedTo, Gilaki]
  • A. Gilaki chosen
    Gilaki is an Iranian language spoken primarily in Iran’s Gilan Province along the Caspian Sea coast.
  • B. Bakhtiari Luri
    Bakhtiari Luri is a major Southwestern Iranian dialect spoken primarily by the Bakhtiari people of western and southwestern Iran.
  • C. Mazanderani language
    Mazanderani language is a Northwestern Iranian language spoken primarily along Iran’s southern Caspian Sea coast, especially in Mazandaran Province.
  • D. Northern Luri
    Northern Luri is a major variety of the Luri language spoken by Lur communities in western Iran, distinguished by its own phonological and lexical features.
  • E. Central Luri
    Central Luri is a major variety of the Luri language spoken by Lur communities in western Iran, characterized by features transitional between Persian and Kurdish.
  • 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_69d87f23bb088190a16fbb91a1957ea5 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e25e31c9e8819094593f3aeb44f2ca completed April 17, 2026, 4:22 p.m.
NED1 Entity disambiguation (via context triple) batch_6a001f9fb2908190a8521b1ccf49170a completed May 10, 2026, 6:03 a.m.
Created at: April 10, 2026, 5:06 a.m.