Triple
T37624299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Publius Septimius Geta |
E936160
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman provincial elite |
C8585
|
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: Roman provincial elite Context triple: [Publius Septimius Geta, instanceOf, Roman provincial elite]
-
A.
Roman imperial household
The Roman imperial household comprised the emperor’s family, slaves, freedmen, and administrative staff who managed both the private affairs and many public functions of the imperial court.
-
B.
Roman aristocratic lineage
A Roman aristocratic lineage is a hereditary elite family line in ancient Rome, distinguished by noble ancestry, political influence, social prestige, and the transmission of status, wealth, and public offices across generations.
-
C.
Roman aristocrat
chosen
A Roman aristocrat is a wealthy, high-status citizen of ancient Rome who wields political influence, owns extensive land and slaves, and upholds traditional social and cultural norms of the elite.
-
D.
Roman aristocrat
A Roman aristocrat is a wealthy, high-status citizen of ancient Rome who wields political, social, and economic power through land ownership, patronage networks, and participation in public life.
-
E.
Roman provincial culture
Roman provincial culture refers to the diverse local societies within the Roman Empire that blended indigenous traditions with Roman political, legal, religious, and material influences, producing varied yet interconnected regional identities.
- 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.