Triple
T28831910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artsruni dynasty |
E728072
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Armenian noble family |
C34459
|
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 family Context triple: [Artsruni dynasty, instanceOf, Armenian noble family]
-
A.
Albanian noble family
An Albanian noble family is a historically prominent lineage from Albania, typically holding hereditary titles, land, and political influence within regional or national power structures.
-
B.
Georgian noble family
A Georgian noble family is a hereditary lineage from Georgia historically endowed with social prestige, land, and political influence within the country’s aristocratic hierarchy.
-
C.
Hungarian noble family
A Hungarian noble family is a historically recognized lineage within the Kingdom of Hungary’s aristocracy, holding hereditary titles, lands, and social privileges passed down through generations.
-
D.
Ottoman Armenian family
An Ottoman Armenian family is a kinship unit of Armenian ethnicity living within the Ottoman Empire, shaped by a blend of Armenian cultural traditions, communal institutions, and the legal, social, and economic structures of Ottoman society.
-
E.
Armenian dynasty
chosen
An Armenian dynasty is a hereditary ruling family originating from Armenia that held political power and authority over Armenian territories during a specific historical period.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:38 a.m.