Triple
T3311074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cassandane |
E69572
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Achaemenid dynasty noble |
C811
|
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: Achaemenid dynasty noble Context triple: [Cassandane, instanceOf, Achaemenid dynasty noble]
-
A.
Achaemenid ruler
An Achaemenid ruler is a monarch of the ancient Persian Achaemenid Empire who exercised centralized authority over a vast, multicultural territory through a system of satrapies, royal roads, and imperial administration.
-
B.
noble family
chosen
A noble family is a socially and often legally recognized kinship group that holds hereditary titles, privileges, and status within a hierarchical society, typically associated with landownership, political influence, and longstanding lineage.
-
C.
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.
-
D.
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.
-
E.
Isma'ili dynasty
The Isma'ili dynasty refers to a series of Muslim ruling families and states historically led or influenced by Isma'ili Shi'a communities, most notably the Fatimid Caliphate, which combined religious leadership with political authority.
- 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_69ad859f218081909458d2cebbf57565 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:11 p.m.