Triple

T30108547
Position Surface form Disambiguated ID Type / Status
Subject dux Daciae Ripensis E765197 entity
Predicate instanceOf P0 FINISHED
Object late Roman military office C23723 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: late Roman military office
Context triple: [dux Daciae Ripensis, instanceOf, late Roman military office]
  • A. Roman military office chosen
    A Roman military office is an administrative and command position within the Roman armed forces responsible for organizing, directing, and managing soldiers, resources, and military operations.
  • B. Praetorian prefect
    A Praetorian prefect was a high-ranking official in the Roman Empire who originally commanded the Praetorian Guard and later evolved into a powerful administrative and judicial authority overseeing major regions of the empire.
  • C. 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.
  • D. Roman official
    A Roman official is a government functionary of ancient Rome responsible for administering laws, finances, justice, or public works within the Republic or Empire.
  • 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.

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_69f22475ad7c8190be7f9541044a0bbb completed April 29, 2026, 3:32 p.m.
Created at: April 29, 2026, 7:10 p.m.