Triple
T14852484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hemony family |
E349264
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dutch-Flemish family |
C12592
|
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: Dutch-Flemish family Context triple: [Hemony family, instanceOf, Dutch-Flemish family]
-
A.
Dutch patrician family
chosen
A Dutch patrician family is a historically prominent, often urban-based lineage belonging to the higher bourgeois elite of the Netherlands, distinguished by long-standing social status, wealth, and influence in commerce, politics, or culture.
-
B.
Belgian family
A Belgian family is a household unit typically composed of individuals related by blood, marriage, or partnership, living in Belgium and shaped by the country’s multicultural, multilingual, and socially supportive context.
-
C.
Dutch American
A Dutch American is a person in the United States who has full or partial ancestral roots in the Netherlands, often blending Dutch cultural traditions with American society and identity.
-
D.
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.
-
E.
Dutch bourgeoisie
The Dutch bourgeoisie were the urban middle-class merchants, professionals, and civic leaders who, from the early modern period onward, shaped the Netherlands’ commercial prosperity, cultural life, and political institutions through their wealth, Calvinist-influenced values, and emphasis on civic responsibility.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:54 a.m.