Triple
T4698914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orestes, prefect of Alexandria |
E104217
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | praefectus Augustalis |
C16220
|
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: praefectus Augustalis Context triple: [Orestes, prefect of Alexandria, instanceOf, praefectus Augustalis]
-
A.
praetor
A praetor is a high-ranking Roman magistrate responsible for administering justice, commanding armies, and governing provinces within the Roman Republic and early Empire.
-
B.
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.
-
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.
imperial prince of Rome
An imperial prince of Rome is a male member of the ruling emperor’s family, often positioned as a potential heir and endowed with high status, privileges, and political influence within the Roman imperial hierarchy.
-
E.
patrician of the Western Roman Empire
A patrician of the Western Roman Empire is a member of the hereditary aristocratic elite who wielded significant political, social, and economic influence within the imperial hierarchy and Roman society.
- 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:17 p.m.