Triple

T8377581
Position Surface form Disambiguated ID Type / Status
Subject Eastern Roman provinces E197613 entity
Predicate instanceOf P0 FINISHED
Object Roman provincial divisions 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: Roman provincial divisions
Context triple: [Eastern Roman provinces, instanceOf, Roman provincial divisions]
  • A. 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.
  • B. late Roman provincial governor
    A late Roman provincial governor was an imperial official responsible for administering a province’s civil government, justice, taxation, and local defense under the increasingly centralized and bureaucratic structures of the later Roman Empire.
  • C. Roman auxiliary units
    Roman auxiliary units were non-citizen military formations that supported the legions by providing specialized troops—such as infantry, cavalry, and archers—from diverse provincial populations across the empire.
  • D. 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.
  • E. Roman imperial policy
    Roman imperial policy refers to the strategies, laws, and administrative practices employed by Roman emperors to maintain control, integrate diverse provinces, manage resources, and project power across the empire.
  • 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_69ca82f64c188190af4e1608036b865d completed March 30, 2026, 2:04 p.m.
Created at: March 30, 2026, 6:02 p.m.