Triple
T22042840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sibylla of Armenia |
E544681
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Armenian person |
C18629
|
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 person Context triple: [Sibylla of Armenia, instanceOf, medieval Armenian person]
-
A.
Armenian person
chosen
An Armenian person is an individual who identifies with the Armenian nation, typically sharing its historical heritage, cultural traditions, and often the Armenian language, whether living in Armenia or in the global diaspora.
-
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.
Ottoman-Armenian person
An Ottoman-Armenian person is an individual of Armenian ethnic origin who lived in or held citizenship of the Ottoman Empire, shaped by its multicultural, multilingual, and often politically turbulent context.
-
D.
Armenian saint
An Armenian saint is a holy figure recognized within the Armenian Apostolic or Armenian Catholic traditions for exemplary faith, virtue, and often martyrdom, and venerated as an intercessor and spiritual model for the faithful.
-
E.
medieval Georgian noblewoman
A medieval Georgian noblewoman is an aristocratic woman of the Georgian kingdoms who held social status, land-related privileges, and dynastic responsibilities within the feudal and courtly structures of the Middle Ages.
- 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:25 p.m.