Triple
T28938205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gagik I Artsruni |
E730374
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Artsruni dynasty |
C55426
|
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 Artsruni dynasty Context triple: [Gagik I Artsruni, instanceOf, member of the Artsruni 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.
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.
-
D.
member of the Arsacid dynasty of Armenia
A member of the Arsacid dynasty of Armenia is an individual belonging to the royal house that ruled the Armenian kingdom from the 1st to the 5th century CE, often serving as king or high-ranking noble within its hereditary monarchical structure.
-
E.
member of the Abkhazian dynasty
A member of the Abkhazian dynasty is an individual belonging by birth or marriage to the ruling royal house that governed the medieval Kingdom of Abkhazia and its successor realms in the Caucasus.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 8:34 a.m.