Triple
T3265654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sejanus |
E68521
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman |
C12577
|
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 Context triple: [Sejanus, instanceOf, ancient Roman]
-
A.
Roman dynasty
A Roman dynasty is a succession of rulers from the same family or lineage who governed the Roman state over a continuous period, shaping its political, social, and cultural development.
-
B.
ancient Greek
An ancient Greek is a person from the civilizations of classical Greece, typically characterized by participation in city-state life, polytheistic religion, and contributions to early Western philosophy, art, and politics.
-
C.
ancient empire
An ancient empire is a large, centralized civilization from antiquity that exerts political, military, economic, and cultural control over diverse territories and peoples under a single dominant authority.
-
D.
Roman imperial dynasty
A Roman imperial dynasty is a succession of emperors from the same family or household who ruled the Roman Empire over a continuous period, sharing political power, legitimacy, and often common policies or agendas.
-
E.
client state of the Roman Empire
A client state of the Roman Empire was a formally independent polity that maintained its own rulers and internal administration while being bound by treaty to support Roman foreign policy, pay tribute or provide troops, and accept Roman influence over its succession and external affairs.
- 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_69ad8590444081909e8107a8aeef3a23 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:09 p.m.