Triple

T8365966
Position Surface form Disambiguated ID Type / Status
Subject Vaspurakan E197126 entity
Predicate instanceOf P0 FINISHED
Object Armenian principality C23948 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: Armenian principality
Context triple: [Vaspurakan, instanceOf, Armenian principality]
  • A. Turkish principality
    A Turkish principality is a semi-independent, territorially defined political entity ruled by a Turkish dynastic leader, typically emerging in the medieval or early modern period within the broader context of Turkic state formation and regional power dynamics.
  • B. medieval Armenian kingdom
    A medieval Armenian kingdom is a historically situated political entity in the Armenian Highlands, characterized by Armenian dynastic rule, Christian cultural identity, and feudal socio-political structures interacting with neighboring empires.
  • C. medieval Georgian principality
    A medieval Georgian principality is a semi-autonomous territorial domain within the historical Kingdom of Georgia, ruled by a local prince or noble dynasty that exercised regional political, military, and economic authority while recognizing the suzerainty of a higher Georgian monarch or overlord.
  • D. Russian principality
    A Russian principality is a semi-autonomous medieval or early modern territorial state ruled by a prince within the broader political and cultural sphere of Rus', often owing allegiance to a grand prince or tsar.
  • E. Catalan principality
    A Catalan principality is a medieval or early modern political entity in which Catalan-speaking territories were governed by a prince or similar sovereign authority, often within larger composite monarchies.
  • F. None of above. chosen

Provenance (1 batch)

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_69ca82f2dbe48190aba982e75a0d94de completed March 30, 2026, 2:04 p.m.
Created at: March 30, 2026, 6 p.m.