Triple
T8771027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rusudan of Armenia |
E208460
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval 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: medieval Armenian noble Context triple: [Rusudan of Armenia, instanceOf, medieval 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.
medieval Armenian kingdom
A medieval Armenian kingdom is a historically situated political entity in the Armenian Highlands, characterized by Armenian dynastic rule, Christian cultural identity, and feudal socio-political structures interacting with neighboring empires.
-
C.
nobleman
A nobleman is a male member of the aristocracy who holds a hereditary or granted title, social privileges, and often land or political influence within a hierarchical society.
-
D.
Swedish noble
A Swedish noble is a member of Sweden’s historically privileged aristocratic estate, traditionally holding hereditary titles, social status, and often land or political influence within the Swedish realm.
-
E.
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.
- 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_69ca835edb4481909b4aafb616dc5eb7 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:41 p.m.