Triple
T36024158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Van Teylingen family |
E1042077
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Dutch noble lineage |
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: medieval Dutch noble lineage Context triple: [Van Teylingen family, instanceOf, medieval Dutch noble lineage]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
medieval English noble dynasty
A medieval English noble dynasty is a powerful hereditary family line that held titles, lands, and political influence across generations in England during the Middle Ages.
-
E.
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.
- 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_69f76e2c568881909e1e21f85252b0f0 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.