Triple

T20557355
Position Surface form Disambiguated ID Type / Status
Subject Abaza E504752 entity
Predicate hasAlternativeName P39 FINISHED
Object Abazian 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: Abazian | Statement: [Abaza, hasAlternativeName, Abazian]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Abazian
Context triple: [Abaza, hasAlternativeName, Abazian]
  • A. Abaza chosen
    Abaza is a Northwest Caucasian language spoken primarily in the Russian Republic of Karachay-Cherkessia, known for its complex consonant system and rich verbal morphology.
  • B. Asbarez
    Asbarez is a long-running Armenian-American newspaper that serves as a key news source and voice for the Armenian diaspora, particularly in the United States.
  • C. Ghukasyan
    Ghukasyan is an Armenian surname most notably borne by Arkadi Ghukasyan, a former president of the Republic of Artsakh (Nagorno-Karabakh).
  • D. Akhuryan
    Akhuryan is a town in northwestern Armenia situated near the Akhuryan River and close to the city of Gyumri.
  • E. Akhurian
    Akhurian is a village located in Armenia’s northwestern Shirak Province, near the border with Turkey.
  • 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_69e0b4b6587c8190aee63dc7cff244ea completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a5de9c008190b8620628fb285e90 completed April 20, 2026, 10:17 p.m.
Created at: April 16, 2026, 11:38 a.m.