Triple
T14941087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nero Julius Caesar |
E372527
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman heir apparent |
C28035
|
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 heir apparent Context triple: [Nero Julius Caesar, instanceOf, Roman heir apparent]
-
A.
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.
-
B.
member of the Roman imperial family
chosen
A member of the Roman imperial family is an individual related by blood, marriage, or adoption to the reigning emperor, often holding elevated social status, political influence, and potential claims to succession within the Roman Empire.
-
C.
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.
-
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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:38 a.m.