Triple
T9716879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rex Sacrorum |
E235163
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman religious office |
C10539
|
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: ancient Roman religious office Context triple: [Rex Sacrorum, instanceOf, ancient Roman religious office]
-
A.
ancient Roman title
chosen
An ancient Roman title is a formal designation or rank used in Roman society and government to denote an individual's official role, status, or authority within the political, military, religious, or social hierarchy.
-
B.
Roman military office
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.
-
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 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.
member of the Roman nobility
A member of the Roman nobility is an individual belonging to the elite social class of ancient Rome, distinguished by hereditary status, political influence, and privileged legal and economic rights.
- 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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:20 p.m.