Triple
T13207770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radbot of Habsburg |
E314409
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 11th-century Swiss noble |
C32645
|
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: 11th-century Swiss noble Context triple: [Radbot of Habsburg, instanceOf, 11th-century Swiss noble]
-
A.
member of the House of Kyburg
A member of the House of Kyburg is an individual belonging to the medieval Swiss noble dynasty that held significant territorial and political power in parts of present-day Switzerland during the High Middle Ages.
-
B.
Austrian noble
An Austrian noble is a member of the historical aristocracy of Austria, typically holding hereditary titles, land, and social privileges within the Habsburg and later Austrian realms.
-
C.
member of the House of Lorraine
A member of the House of Lorraine is an individual belonging by birth or legitimate descent to the historic European noble dynasty that ruled the Duchy of Lorraine and later held significant royal and imperial titles.
-
D.
Count of Savoy
The Count of Savoy is a noble title historically held by the ruler of the County of Savoy, a medieval and early modern territorial principality in the Western Alps that later formed the core of the House of Savoy’s dynastic power.
-
E.
Alsatian noble house
An Alsatian noble house is an aristocratic family originating from the Alsace region, historically holding hereditary titles, lands, and political influence within the shifting sovereignties of France and the Holy Roman Empire.
- 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:17 p.m.