Triple
T28607376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khosrovidukht |
E724088
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Armenian noblewoman |
C51598
|
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 noblewoman Context triple: [Khosrovidukht, instanceOf, Armenian noblewoman]
-
A.
Armenian princess
chosen
An Armenian princess is a noblewoman of royal Armenian lineage, historically associated with the ruling dynasties of Armenia and often involved in political alliances, cultural patronage, and the preservation of Armenian heritage.
-
B.
Byzantine noblewoman
A Byzantine noblewoman is an elite woman of the Eastern Roman Empire, distinguished by her high social rank, wealth, and influence within the imperial court, religious life, and family alliances.
-
C.
Georgian noblewoman
A Georgian noblewoman is an aristocratic woman from the historical region of Georgia, typically characterized by high social status, landownership, and influence within the political and cultural life of Georgian society.
-
D.
Bulgarian noblewoman
A Bulgarian noblewoman is a high-born woman from Bulgaria’s aristocratic or ruling classes, historically associated with landownership, political influence, and cultural patronage.
-
E.
Serbian noblewoman
A Serbian noblewoman is a high-born woman from Serbian society, historically belonging to the aristocracy and often involved in political, cultural, or social affairs of her time.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:28 a.m.