Triple
T37383651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evertsen family |
E928504
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dutch naval family |
C27455
|
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 naval family Context triple: [Evertsen family, instanceOf, Dutch naval family]
-
A.
Dutch patrician family
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.
Dutch privateers
Dutch privateers were privately owned, state-authorized armed vessels from the Dutch Republic that attacked and captured enemy ships, especially during the 16th to 18th centuries, to disrupt rival trade and bolster Dutch maritime power.
-
C.
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.
-
D.
Flemish dynasty
The Flemish dynasty refers to the line of medieval rulers and noble families that governed the County of Flanders and surrounding regions, significantly influencing the political, economic, and cultural development of northwestern Europe.
-
E.
shipowning family
chosen
A shipowning family is a lineage-based group that collectively owns, manages, and derives income from one or more commercial vessels, often integrating maritime business decisions with family governance and succession.
- 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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.