Triple
T15233569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles I of Hungary |
E364065
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Capetian House of Anjou member |
C10902
|
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: Capetian House of Anjou member Context triple: [Charles I of Hungary, instanceOf, Capetian House of Anjou member]
-
A.
Capetian dynasty member
chosen
A Capetian dynasty member is an individual belonging by blood or legitimate descent to the royal house founded by Hugh Capet, which ruled France and various European realms from the late 10th century onward.
-
B.
House of Hohenstaufen member
A House of Hohenstaufen member is an individual belonging to the medieval German noble dynasty that produced several Holy Roman Emperors and kings of Germany, Italy, and Sicily between the 12th and 13th centuries.
-
C.
House of Valois-Anjou
The House of Valois-Anjou was a cadet branch of the French royal Valois dynasty that held titles in Anjou, Naples, and Provence, playing a significant role in late medieval French and Italian politics.
-
D.
member of the Hauteville family
A member of the Hauteville family is an individual belonging to the medieval Norman dynasty founded by Tancred of Hauteville, whose descendants played a major role in the conquest and rule of southern Italy and Sicily.
-
E.
House of Habsburg member
A House of Habsburg member is an individual belonging by birth or marriage to the historic European royal dynasty that ruled vast territories including Austria, Spain, and the Holy Roman Empire.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:12 a.m.