Triple
T9422902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conrad the Younger |
E227198
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Salian dynasty member |
C26123
|
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: Salian dynasty member Context triple: [Conrad the Younger, instanceOf, Salian dynasty member]
-
A.
member of the Khalji dynasty
A member of the Khalji dynasty is an individual belonging to the Turkic-origin ruling family that controlled the Delhi Sultanate in northern India during the late 13th and early 14th centuries.
-
B.
Herodian dynasty member
A Herodian dynasty member is an individual belonging to the ruling family established by Herod the Great, which governed Judea and surrounding regions under Roman authority during the late first century BCE and early first century CE.
-
C.
member of the Tughlaq dynasty
A member of the Tughlaq dynasty is an individual belonging to the medieval Muslim ruling family that governed the Delhi Sultanate in northern India during the 14th century, known for ambitious reforms, extensive territorial control, and periods of political instability.
-
D.
member of the Ottoman dynasty
A member of the Ottoman dynasty is an individual belonging by birth or marriage to the ruling imperial family of the Ottoman Empire, historically entitled to varying degrees of political influence, privilege, and succession rights.
-
E.
member of the Jochid dynasty
A member of the Jochid dynasty is an individual descended from Jochi, the eldest son of Genghis Khan, belonging to the ruling lineage that governed the Golden Horde and related successor states.
- F. None of above. chosen
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_69ca8436ba308190903e470776d2d893 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:48 p.m.