Triple
T3617790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constantine VI |
E76644
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Isaurian dynasty ruler |
C13500
|
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: Isaurian dynasty ruler Context triple: [Constantine VI, instanceOf, Isaurian dynasty ruler]
-
A.
Byzantine imperial dynasty
A Byzantine imperial dynasty is a succession of related rulers who governed the Eastern Roman (Byzantine) Empire, shaping its political, religious, and cultural life over multiple generations.
-
B.
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.
-
C.
member of the Constantinian dynasty
A member of the Constantinian dynasty is an individual belonging to the imperial family that ruled the Roman Empire from the rise of Constantine the Great in the early 4th century until the death of his descendants later that century.
-
D.
Ptolemaic ruler
A Ptolemaic ruler is a monarch from the Macedonian Greek dynasty that governed Egypt and surrounding territories from the late 4th century BCE to the Roman conquest, blending Hellenistic and Egyptian political and cultural traditions.
-
E.
5th-century ruler
A 5th-century ruler is a sovereign or dominant political leader who governed a state or territory during the 400s CE, navigating the era’s shifting empires, invasions, and cultural transformations.
- 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:23 p.m.