Triple
T9087364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Licinius Lucullus |
E217792
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | governor of a Roman province |
C25583
|
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: governor of a Roman province Context triple: [Lucius Licinius Lucullus, instanceOf, governor of a Roman province]
-
A.
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.
-
B.
praefectus Augustalis
The praefectus Augustalis was the Roman imperial governor of Egypt, a high-ranking equestrian official directly appointed by the emperor to administer the province’s civil, judicial, and financial affairs.
-
C.
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.
-
D.
Judean official
A Judean official is a governmental or administrative authority from ancient Judea responsible for overseeing civic, legal, or religious affairs within the region.
-
E.
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.
- 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_69ca83d8ab5881909d8fddae363b32b1 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:13 p.m.