Triple
T13915460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afshar (Afsharid-related) lineage |
E334609
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical dynasty-related lineage |
C14509
|
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: historical dynasty-related lineage Context triple: [Afshar (Afsharid-related) lineage, instanceOf, historical dynasty-related lineage]
-
A.
dynastic affiliation category
A dynastic affiliation category classifies entities—such as individuals, artifacts, or events—according to their association with a specific ruling dynasty or hereditary line of power.
-
B.
dynastic history
Dynastic history is the study and narrative of successive ruling families, their power transitions, political structures, and cultural impacts over time within a particular region or civilization.
-
C.
dynasty
A dynasty is a succession of rulers or leaders from the same family or lineage, often maintaining power over multiple generations within a state or organization.
-
D.
dynastic branch
chosen
A dynastic branch is a subordinate line of a ruling or noble family that descends from a common ancestor but forms its own distinct lineage within the broader dynasty.
-
E.
dynasty of heralds
A dynasty of heralds is a long-standing lineage devoted to announcing, recording, and ceremonially representing the deeds, titles, and transitions of power within and between realms.
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:16 p.m.