Triple
T28971556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashot Msaker |
E734287
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bagratuni dynasty member |
C24021
|
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: Bagratuni dynasty member Context triple: [Ashot Msaker, instanceOf, Bagratuni dynasty member]
-
A.
Bagratid dynasty member
chosen
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.
-
B.
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.
-
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 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.
-
E.
branch of the Bagrationi dynasty
A branch of the Bagrationi dynasty is a distinct familial line descending from the historic Georgian royal house, often associated with specific territories, titles, or periods of rule.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 9:06 a.m.