Triple
T26458502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salome of Armenia |
E665559
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Arsacid dynasty of Armenia |
C51599
|
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 Arsacid dynasty of Armenia Context triple: [Salome of Armenia, instanceOf, member of the Arsacid dynasty of Armenia]
-
A.
Member of the Orontid dynasty
A Member of the Orontid dynasty is an individual belonging to the ancient Armenian royal house that ruled parts of Armenia and neighboring regions from the Achaemenid through the Hellenistic periods.
-
B.
member of the Germiyanid dynasty
A member of the Germiyanid dynasty is an individual belonging to the medieval Anatolian Turkish ruling family that governed the Beylik of Germiyan from the late 13th to the early 15th century.
-
C.
Bagratid dynasty member
A Bagratid dynasty member is an individual belonging to the medieval royal family of Armenian and Georgian origin that ruled various Caucasian kingdoms between the 9th and 11th centuries.
-
D.
member of the Battiad dynasty
A member of the Battiad dynasty is an individual belonging to the royal lineage that ruled the ancient Greek city-state of Cyrene in North Africa, traditionally founded by Battus I and his descendants.
-
E.
member of the Isaurian dynasty
A member of the Isaurian dynasty is an individual belonging to the Byzantine imperial family that ruled from the 8th to early 9th century, originating from the Isauria region in Asia Minor and known for initiating major religious and administrative reforms.
- 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 27, 2026, 12:10 a.m.