Triple

T21866633
Position Surface form Disambiguated ID Type / Status
Subject Regio XII Piscina Publica E539898 entity
Predicate instanceOf P0 FINISHED
Object regio of Rome under Augustus C45440 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: regio of Rome under Augustus
Context triple: [Regio XII Piscina Publica, instanceOf, regio of Rome under Augustus]
  • A. Roman proconsul
    A Roman proconsul was a former consul granted extended imperium to govern a province, command armies, and administer justice on behalf of the Roman state.
  • B. governor of a Roman province
    A governor of a Roman province was an appointed official, often of senatorial or equestrian rank, responsible for administering justice, collecting taxes, commanding military forces, and maintaining order within a defined territorial unit of the Roman state.
  • C. Roman censor
    A Roman censor was a high-ranking magistrate responsible for conducting the census, overseeing public morals, and managing certain aspects of state finances and public works in the Roman Republic.
  • D. 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.
  • E. 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.
  • 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_69e0c478f59081909d54302b57fc1ce3 completed April 16, 2026, 11:14 a.m.
Created at: April 16, 2026, 6:56 p.m.