Triple

T22241202
Position Surface form Disambiguated ID Type / Status
Subject Yazgulyam E549726 entity
Predicate hasAlternativeName P39 FINISHED
Object Yazgulom 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: Yazgulom | Statement: [Yazgulyam, hasAlternativeName, Yazgulom]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yazgulom
Context triple: [Yazgulyam, hasAlternativeName, Yazgulom]
  • A. Yazgulyam chosen
    Yazgulyam is a rare and highly conservative Eastern Iranian language spoken in the Yazgulyam Valley of Tajikistan.
  • B. Gelemiş
    Gelemiş is a small village in southwestern Turkey that serves as the modern settlement closest to the ancient Lycian city and beach of Patara.
  • C. Gökalp
    Gökalp is a Turkish surname most prominently associated with Ziya Gökalp, an influential early 20th-century sociologist, writer, and ideologue of Turkish nationalism.
  • D. Kampilya
    Kampilya was an ancient city in northern India, historically renowned as the capital of the Panchala kingdom mentioned in the Indian epics.
  • E. Tevfikiye
    Tevfikiye is a village in northwestern Turkey located close to the archaeological site of Hisarlik, widely identified with ancient Troy.
  • 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_69e11e41d9408190bd770cf282e22753 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f132140ed481909ab0d4022756a4ba completed April 28, 2026, 10:17 p.m.
Created at: April 16, 2026, 8:38 p.m.