Triple
T8330582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flavius Julius Crispus |
E195063
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman imperial prince |
C13748
|
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 imperial prince Context triple: [Flavius Julius Crispus, instanceOf, Roman imperial prince]
-
A.
imperial prince of Rome
chosen
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.
-
B.
Roman imperial princess
A Roman imperial princess is a female member of the emperor’s family whose status, marriages, and public image were used to secure dynastic legitimacy and political alliances within the Roman Empire.
-
C.
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.
-
D.
member of the Flavian dynasty
A member of the Flavian dynasty is an individual belonging to the Roman imperial family that ruled the Roman Empire from 69 to 96 CE, including emperors Vespasian, Titus, and Domitian and their close relatives.
-
E.
Roman client ruler
A Roman client ruler was a local king or chieftain who retained nominal authority over their territory while governing under the supervision and in the interests of the Roman Empire.
- 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_69ca82e87f2c8190bdb71ee29dfc642d |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:56 p.m.