Triple
T19444087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teimuraz II of Kakheti |
E486427
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bagrationi dynasty member |
C41762
|
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: Bagrationi dynasty member Context triple: [Teimuraz II of Kakheti, instanceOf, Bagrationi dynasty member]
-
A.
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.
-
B.
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.
-
C.
member of the Rurik dynasty
A member of the Rurik dynasty is an individual belonging to the medieval ruling family traditionally traced to the Varangian prince Rurik, which governed parts of Eastern Europe, including Kievan Rus and later principalities, from the 9th to the 16th centuries.
-
D.
Jagiellonian dynasty member
A Jagiellonian dynasty member is an individual belonging to the royal house that ruled parts of Central and Eastern Europe, including Poland, Lithuania, Bohemia, and Hungary, from the late 14th to the 16th century.
-
E.
Luxembourg dynasty member
A Luxembourg dynasty member is an individual belonging to the medieval European royal House of Luxembourg, which produced several Holy Roman Emperors, kings, and high-ranking nobles.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:38 p.m.