Triple

T18322175
Position Surface form Disambiguated ID Type / Status
Subject Ingush people E438909 entity
Predicate autonym P1435 FINISHED
Object Ghalghai 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: Ghalghai | Statement: [Ingush people, autonym, Ghalghai]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ghalghai
Context triple: [Ingush people, autonym, Ghalghai]
  • A. Ghalghai chosen
    Ghalghai is the self-designation of the Ingush people, a Northeast Caucasian ethnic group native to the North Caucasus region of Russia.
  • B. Khovd
    Khovd is a historically significant city in western Mongolia that serves as a regional cultural and economic center near the Altai Mountains.
  • C. Zalingei
    Zalingei is a major city in the Darfur region of western Sudan, serving as an important administrative and commercial center.
  • D. Zhalantun
    Zhalantun is a county-level city in northeastern Inner Mongolia, China, known for its forests, grasslands, and role as an agricultural and forestry center.
  • E. Khorol
    Khorol is a town in central Ukraine historically situated within the former Poltava Governorate of the Russian Empire.
  • 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_69d8b916a2d081909e249e4902f6aad9 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e50aa7be288190983f13e9c7061b6d completed April 19, 2026, 5:02 p.m.
Created at: April 10, 2026, 10:36 a.m.