Triple
T38672361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William of Egmond |
E943630
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the high nobility of the Low Countries |
C34436
|
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 high nobility of the Low Countries Context triple: [William of Egmond, instanceOf, member of the high nobility of the Low Countries]
-
A.
member of the nobility of the Low Countries
chosen
A member of the nobility of the Low Countries is an individual belonging to the hereditary or formally recognized aristocratic elite of the historical or modern regions comprising present-day Belgium, the Netherlands, and Luxembourg.
-
B.
Dutch nobleman
A Dutch nobleman is a male member of the Netherlands' hereditary or titular nobility, historically holding social status, privileges, and often land or official positions within Dutch society.
-
C.
Belgian aristocrat
A Belgian aristocrat is a member of Belgium’s hereditary nobility, typically bearing a noble title, upholding longstanding family traditions, and often participating in the country’s cultural, social, and sometimes political life.
-
D.
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.
-
E.
Belgian noble house
A Belgian noble house is a hereditary aristocratic family from Belgium, historically recognized with noble titles, privileges, and social status within the country's nobility system.
- 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:33 p.m.