Triple
T34924012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richeza of Lotharingia |
E1007226
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ezzonid dynasty member |
C61861
|
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: Ezzonid dynasty member Context triple: [Richeza of Lotharingia, instanceOf, Ezzonid dynasty member]
-
A.
Attalid dynasty member
An Attalid dynasty member is an individual belonging to the Hellenistic royal family that ruled the kingdom of Pergamon in Asia Minor from the early 3rd to the mid-2nd century BCE.
-
B.
member of the Battiad dynasty
A member of the Battiad dynasty is an individual belonging to the royal lineage that ruled the ancient Greek city-state of Cyrene in North Africa, traditionally founded by Battus I and his descendants.
-
C.
Salian dynasty member
A Salian dynasty member is an individual belonging to the German royal and imperial family that ruled the Holy Roman Empire from 1024 to 1125, originating from the Frankish nobility along the Rhine.
-
D.
Member of the Orontid dynasty
A Member of the Orontid dynasty is an individual belonging to the ancient Armenian royal house that ruled parts of Armenia and neighboring regions from the Achaemenid through the Hellenistic periods.
-
E.
Hethumid dynasty member
A Hethumid dynasty member is an individual belonging to the medieval Armenian royal house of Cilician Armenia, holding lineage, titles, or roles associated with the Hethumid ruling family.
- 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_69f76dc3d83881909d5c3c14455cfa2c |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.