Triple
T8782365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruben I of Armenia |
E208760
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Armenian noble |
C24022
|
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 noble Context triple: [Ruben I of Armenia, instanceOf, Armenian noble]
-
A.
Armenian prince
chosen
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.
-
B.
Achaemenid noble
An Achaemenid noble is a high-ranking member of the Persian aristocracy who held land, military command, and administrative authority under the Achaemenid Empire, often serving as a close supporter and regional representative of the Great King.
-
C.
Serbian nobleman
A Serbian nobleman is a member of the historical or contemporary Serbian aristocracy, typically holding hereditary titles, land, and social privileges within Serbian society.
-
D.
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.
-
E.
Ottoman Albanian noble
An Ottoman Albanian noble was a member of the Albanian-origin elite within the Ottoman Empire who held hereditary or state-granted titles, land, and administrative or military authority, often serving as intermediaries between the central government and local populations.
- 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_69ca835fbee88190bf625939bac48d7f |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:42 p.m.