Triple

T5285900
Position Surface form Disambiguated ID Type / Status
Subject Lazica E119617 entity
Predicate instanceOf P0 FINISHED
Object Byzantine client state C18315 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: Byzantine client state
Context triple: [Lazica, instanceOf, Byzantine client state]
  • A. client state of the Roman Empire
    A client state of the Roman Empire was a formally independent polity that maintained its own rulers and internal administration while being bound by treaty to support Roman foreign policy, pay tribute or provide troops, and accept Roman influence over its succession and external affairs.
  • B. client state of the Roman Republic
    A client state of the Roman Republic was a formally independent polity that, through treaties or coercion, accepted Roman supremacy in foreign policy, military support, and often internal affairs in exchange for protection and limited autonomy.
  • C. Byzantine law code
    A Byzantine law code is a systematically organized collection of legal rules, imperial edicts, and judicial interpretations that governed civil, criminal, and ecclesiastical matters in the Byzantine Empire.
  • D. Neo-Byzantine building
    A Neo-Byzantine building is a structure designed in a revival style that draws on medieval Byzantine architecture, featuring elements such as domes, rounded arches, rich ornamentation, and often elaborate brick or stonework.
  • E. Athenian public works program
    Athenian public works program: A state-sponsored initiative in classical Athens that funded large-scale construction, infrastructure, and artistic projects—often employing citizens and metics—to enhance civic life, display communal wealth and power, and provide economic support.
  • 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_69bd446de5648190b313a90bd96730d2 completed March 20, 2026, 12:58 p.m.
Created at: March 20, 2026, 1:52 p.m.