Triple
T15206938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippe de Croÿ, Duke of Aarschot |
E363412
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the House of Croÿ |
C36285
|
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 House of Croÿ Context triple: [Philippe de Croÿ, Duke of Aarschot, instanceOf, member of the House of Croÿ]
-
A.
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.
-
B.
House of Lorraine member
A House of Lorraine member is an individual belonging by birth or legitimate descent to the historic European noble dynasty that ruled Lorraine and later provided emperors, kings, and consorts to several major monarchies.
-
C.
member of the House of Valois
A member of the House of Valois is an individual belonging to the French royal dynasty that ruled France and several related territories from the 14th to the 16th centuries.
-
D.
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.
-
E.
member of the Burgundian nobility
A member of the Burgundian nobility is an individual belonging to the hereditary aristocratic elite of the historical Duchy or County of Burgundy, holding land, titles, and social privileges within its feudal hierarchy.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:11 a.m.