Triple
T5973525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Overlander van Purmerland |
E132930
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of Amsterdam regent class |
C9307
|
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 Amsterdam regent class Context triple: [Maria Overlander van Purmerland, instanceOf, member of Amsterdam regent class]
-
A.
person from Amsterdam
A person from Amsterdam is an individual who resides in or originates from the city of Amsterdam, typically shaped by its multicultural, urban, and historically rich environment.
-
B.
borough of Amsterdam
A borough of Amsterdam is an administrative subdivision of the city that manages local governance, services, and regulations for its designated district within the municipality.
-
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.
Dutch regent
chosen
A Dutch regent was a member of the wealthy urban patrician elite who governed cities and provinces in the Dutch Republic, often holding multiple civic offices and exerting significant political and economic influence.
-
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_69c0086deab081908550159ca23eec9b |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:03 p.m.