Triple
T8173972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William II of Apulia |
E190895
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Hauteville dynasty |
C16746
|
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: member of the Hauteville dynasty Context triple: [William II of Apulia, instanceOf, member of the Hauteville dynasty]
-
A.
member of the Hauteville family
chosen
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.
-
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.
Capetian dynasty member
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.
-
D.
member of the Babenberg dynasty
A member of the Babenberg dynasty is an individual belonging to the medieval noble family that ruled Austria and parts of Central Europe from the 10th to the mid-13th century.
-
E.
Carolingian dynasty member
A Carolingian dynasty member is an individual belonging to the Frankish royal family that ruled large parts of Western and Central Europe from the 8th to 10th centuries, originating with Charles Martel and reaching its height under Charlemagne.
- 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_69ca82c1c0a08190bf8692b4d91a03ca |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:40 p.m.