Triple
T20600542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gurandukht of Abkhazia |
E506166
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Abkhazian dynasty |
C43332
|
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 Abkhazian dynasty Context triple: [Gurandukht of Abkhazia, instanceOf, member of the Abkhazian dynasty]
-
A.
Bagrationi dynasty member
A Bagrationi dynasty member is an individual belonging to the historic royal family that ruled Georgia and related Caucasian realms for centuries, often holding titles of kings, princes, or nobles.
-
B.
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.
-
C.
Gediminid dynasty member
A Gediminid dynasty member is an individual descended from or belonging to the medieval ruling house founded by Grand Duke Gediminas, which governed the Grand Duchy of Lithuania and its successor states.
-
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 Byzantine imperial family
A member of the Byzantine imperial family is an individual related by blood, marriage, or adoption to the reigning emperor, often holding elevated social status, political influence, and potential claims to the throne within the Byzantine Empire.
- 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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:41 a.m.