Triple

T4159665
Position Surface form Disambiguated ID Type / Status
Subject Ирон E91499 entity
Predicate hasAlternativeName P39 FINISHED
Object Iron Ossetic E22457 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: Iron Ossetic | Statement: [Ирон, hasAlternativeName, Iron Ossetic]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Iron Ossetic
Context triple: [Ирон, hasAlternativeName, Iron Ossetic]
  • A. Ossetian language chosen
    The Ossetian language is an Eastern Iranian language spoken primarily in the Caucasus region of Russia, especially in North and South Ossetia.
  • B. Ossetians
    Ossetians are an Iranian-speaking ethnic group native to the central Caucasus, primarily inhabiting the region of Ossetia divided between Russia and Georgia.
  • C. Dargin
    Dargin is a Northeast Caucasian language spoken primarily by the Dargin people in the Republic of Dagestan in Russia.
  • D. Oghur languages
    Oghur languages are an early, now mostly extinct branch of the Turkic language family, historically spoken by steppe peoples such as the Bulgars and Khazars and represented today primarily by Chuvash.
  • E. Lezgian
    Lezgian is a Northeast Caucasian language spoken primarily by the Lezgin people in southern Dagestan and northern Azerbaijan.
  • 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_69aed9626ebc8190a39de631788bea3e completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af029454d08190b7ff32776081fabc completed March 9, 2026, 5:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5c6feae608190b677362d9c734165 completed March 14, 2026, 8:37 p.m.
Created at: March 9, 2026, 3:44 p.m.