Triple
T33400496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inju family |
E855283
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Persian noble family |
C60154
|
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: Persian noble family Context triple: [Inju family, instanceOf, Persian noble family]
-
A.
Iranian noble
chosen
An Iranian noble is a high-ranking member of Iran’s traditional aristocracy, historically distinguished by lineage, landownership, political influence, and social prestige within Persian and later Iranian society.
-
B.
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.
-
C.
Achaemenid noble
An Achaemenid noble is a high-ranking member of the Persian aristocracy who held land, military command, and administrative authority under the Achaemenid Empire, often serving as a close supporter and regional representative of the Great King.
-
D.
Kurdish noble family
A Kurdish noble family is a historically influential lineage of Kurdish origin that holds or has held hereditary social, political, or economic power within Kurdish society or broader regional structures.
-
E.
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.
- 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:35 a.m.