Triple

T5001874
Position Surface form Disambiguated ID Type / Status
Subject Empire of Trebizond E112392 entity
Predicate instanceOf P0 FINISHED
Object Byzantine successor state C16773 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 successor state
Context triple: [Empire of Trebizond, instanceOf, Byzantine successor state]
  • A. successor state of the Western Roman Empire
    A successor state of the Western Roman Empire is a political entity that emerged in its former territories, inheriting and adapting Roman institutions, culture, and legal traditions while developing its own distinct identity.
  • B. successor state of the Western Roman Empire
    A successor state of the Western Roman Empire is a political entity that emerged in former Western Roman territories, inheriting and adapting Roman institutions, culture, and legal traditions while establishing its own distinct governance and identity.
  • C. Byzantine imperial dynasty
    A Byzantine imperial dynasty is a succession of related rulers who governed the Eastern Roman (Byzantine) Empire, shaping its political, religious, and cultural life over multiple generations.
  • D. province of the Byzantine Empire
    A province of the Byzantine Empire was an administrative and territorial unit governed by imperial officials, responsible for local civil, military, and fiscal management under the authority of the central Byzantine state.
  • E. Mongol successor state
    A Mongol successor state is a political entity that emerged from the fragmentation of the Mongol Empire, inheriting its territories, institutions, and ruling elites while developing distinct regional identities and governance structures.
  • 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_69bd4433d0b08190877e83959ef40d81 completed March 20, 2026, 12:57 p.m.
Created at: March 20, 2026, 1:34 p.m.