Triple
T29596107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tigran Honents |
E754302
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Armenian nobleman |
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 nobleman Context triple: [Tigran Honents, instanceOf, medieval Armenian nobleman]
-
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 European noble
A medieval European noble is a high-ranking member of the feudal aristocracy who holds land granted by a monarch in exchange for military service and governance over vassals and peasants.
-
C.
Sasanian noble
A Sasanian noble is a high-ranking member of the aristocratic elite in the Sasanian Empire, holding hereditary land, military, and administrative privileges that underpin imperial governance and social hierarchy.
-
D.
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.
-
E.
Galician nobleman
A Galician nobleman is a member of the hereditary aristocracy originating from the historical region of Galicia, traditionally holding land, titles, and social privileges within its feudal or post-feudal society.
- 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_69f0ef836ac88190bd809dc58b5ec907 |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 6:18 p.m.