Triple

T8312276
Position Surface form Disambiguated ID Type / Status
Subject Diocese of the Britains E194617 entity
Predicate instanceOf P0 FINISHED
Object administrative division of the Roman Empire C5440 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: administrative division of the Roman Empire
Context triple: [Diocese of the Britains, instanceOf, administrative division of the Roman Empire]
  • A. administrative district of the Holy Roman Empire
    An administrative district of the Holy Roman Empire was a territorial unit governed by imperial or local authorities to organize political, judicial, and fiscal control within the Empire’s decentralized structure.
  • B. 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.
  • C. phase of the Roman Empire
    A phase of the Roman Empire is a distinct historical period characterized by specific political structures, territorial extents, social dynamics, and cultural developments within the broader continuum of Roman rule.
  • D. Roman province chosen
    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.
  • E. area of ancient Rome
    An area of ancient Rome is a distinct geographic or administrative section of the city characterized by specific social, political, religious, or economic functions within the broader urban landscape of Roman civilization.
  • 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_69ca82e6e2648190a31eaf6f4f757b2a completed March 30, 2026, 2:04 p.m.
Created at: March 30, 2026, 5:54 p.m.