Triple
T1798308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constantius Chlorus |
E39655
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Constantinian dynasty |
C9082
|
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: member of the Constantinian dynasty Context triple: [Constantius Chlorus, instanceOf, member of the Constantinian dynasty]
-
A.
Herodian dynasty member
A Herodian dynasty member is an individual belonging to the ruling family established by Herod the Great, which governed Judea and surrounding regions under Roman authority during the late first century BCE and early first century CE.
-
B.
member of the House of Romanov
A member of the House of Romanov is an individual belonging by birth or marriage to the former imperial dynasty that ruled Russia from 1613 until the abdication of Tsar Nicholas II in 1917.
-
C.
member of the House of Stuart
A member of the House of Stuart is an individual belonging by birth or legitimate descent to the royal dynasty that ruled Scotland and later England, Great Britain, and Ireland between the late 14th and early 18th centuries.
-
D.
member of the House of Savoy
A member of the House of Savoy is an individual belonging by birth or marriage to the historic European royal dynasty that ruled territories including Savoy, Sardinia, and eventually unified Italy.
-
E.
member of the House of Bourbon
A member of the House of Bourbon is an individual belonging by birth or legitimate descent to the historic European royal dynasty that ruled or influenced several kingdoms, including France, Spain, and Naples.
- 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_69a88632aa588190ba3978fde0db5bbd |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:32 p.m.