Triple

T19064483
Position Surface form Disambiguated ID Type / Status
Subject Tao-Klarjeti E466618 entity
Predicate instanceOf P0 FINISHED
Object medieval Georgian region C16683 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: medieval Georgian region
Context triple: [Tao-Klarjeti, instanceOf, medieval Georgian region]
  • A. medieval Georgian kingdom
    A medieval Georgian kingdom is a feudal Christian monarchy in the Caucasus region characterized by fortified cities, dynastic rule, and a culture shaped by both Eastern and Western influences.
  • B. medieval Georgian principality chosen
    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.
  • C. medieval region
    A medieval region is a geographically defined area during the Middle Ages characterized by distinct political authority, social structures, economic systems, and cultural practices within the broader feudal landscape.
  • D. medieval Georgian noblewoman
    A medieval Georgian noblewoman is an aristocratic woman of the Georgian kingdoms who held social status, land-related privileges, and dynastic responsibilities within the feudal and courtly structures of the Middle Ages.
  • E. 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.
  • F. None of above.

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_69d8dd040fb881909af2a964f65ad208 completed April 10, 2026, 11:20 a.m.
Created at: April 10, 2026, 12:03 p.m.