Triple
T26045997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argead dynasty in Egypt |
E647834
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hellenistic ruling house |
C15338
|
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: Hellenistic ruling house Context triple: [Argead dynasty in Egypt, instanceOf, Hellenistic ruling house]
-
A.
ancient Greek dynasty
An ancient Greek dynasty is a succession of rulers from the same family or lineage who governed a Greek city-state, kingdom, or region over multiple generations in antiquity.
-
B.
Hellenistic-era monarch
chosen
A Hellenistic-era monarch is a ruler who governed one of the successor kingdoms to Alexander the Great’s empire, blending Greek political and cultural traditions with local customs across a diverse, often expansive territory.
-
C.
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.
-
D.
Hellenistic-era kingdom
A Hellenistic-era kingdom is a monarchic state that emerged from the fragmentation of Alexander the Great’s empire, blending Greek political and cultural forms with local traditions across the Eastern Mediterranean and Near East.
-
E.
Isaurian dynasty ruler
An Isaurian dynasty ruler is a Byzantine emperor from the 8th–9th century Isaurian line who governed the Eastern Roman Empire and is often associated with initiating and enforcing the policy of iconoclasm.
- 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_69e77e8d419481908004e6318d28aaab |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 9:10 a.m.