Triple
T28971243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagratuni dynasty |
E734279
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Armenian royal dynasty |
C34459
|
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: Armenian royal dynasty Context triple: [Bagratuni dynasty, instanceOf, Armenian royal dynasty]
-
A.
Armenian dynasty
chosen
An Armenian dynasty is a hereditary ruling family originating from Armenia that held political power and authority over Armenian territories during a specific historical period.
-
B.
Armenian prince
An Armenian prince is a nobleman of Armenia’s historical aristocracy, often ruling a principality or region and serving as a military and political leader within the Armenian kingdom or under foreign suzerainty.
-
C.
King of Armenia
The King of Armenia is the sovereign ruler of the Armenian kingdom, holding supreme political, military, and ceremonial authority over its territories and people.
-
D.
Bulgarian royal dynasty
A Bulgarian royal dynasty is a hereditary ruling family that held the throne of Bulgaria over successive generations, shaping the country's political, cultural, and historical development.
-
E.
Isaurian dynasty ruler
An Isaurian dynasty ruler is a Byzantine emperor from the 8th–9th century Isaurian line who governed the Eastern Roman Empire and is often associated with initiating and enforcing the policy of iconoclasm.
- 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:05 a.m.