Triple
T29707976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruben III of Cilicia |
E751688
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Rubenid dynasty member |
C47553
|
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: Rubenid dynasty member Context triple: [Ruben III of Cilicia, instanceOf, Rubenid 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.
Hethumid dynasty member
chosen
A Hethumid dynasty member is an individual belonging to the medieval Armenian royal house of Cilician Armenia, holding lineage, titles, or roles associated with the Hethumid ruling family.
-
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.
Conradine dynasty member
A Conradine dynasty member is an individual belonging to the early medieval German noble family that held significant power in Franconia and briefly provided a king of East Francia in the 10th century.
-
E.
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.
- 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:28 p.m.