Triple

T2055471
Position Surface form Disambiguated ID Type / Status
Subject Roman army E45664 entity
Predicate instanceOf P0 FINISHED
Object component of the Roman state C7736 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: component of the Roman state
Context triple: [Roman army, instanceOf, component of the Roman state]
  • A. part of the Corpus Juris Civilis
    A part of the Corpus Juris Civilis is a distinct component (such as the Code, Digest, Institutes, or Novels) of the comprehensive body of Roman civil law compiled under Emperor Justinian I.
  • B. Roman province
    A Roman province is an administrative territory outside the Italian peninsula governed by Rome, overseen by appointed officials, and used for taxation, resource extraction, and military control within the Roman Empire.
  • C. 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.
  • D. ancient Roman structure
    An ancient Roman structure is a man-made construction from the Roman civilization, such as temples, amphitheaters, aqueducts, or baths, characterized by advanced engineering, arches, and durable materials like stone and concrete.
  • E. Roman consul
    A Roman consul was one of the two annually elected chief magistrates of the Roman Republic (and later an important office in the Empire), holding supreme civil and military authority and presiding over the Senate and assemblies.
  • 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_69a8891a19508190a12ef1e192308dcb completed March 4, 2026, 7:33 p.m.
Created at: March 4, 2026, 7:40 p.m.