Triple
T22666853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johan Willem Friso Claus Georg Ferdinand von Amsberg |
E559813
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German-born Dutch royal |
C13919
|
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: German-born Dutch royal Context triple: [Johan Willem Friso Claus Georg Ferdinand von Amsberg, instanceOf, German-born Dutch royal]
-
A.
Dutch royal
chosen
A Dutch royal is a member of the Netherlands' reigning House of Orange-Nassau, holding constitutional, ceremonial, and representative roles within the Dutch monarchy.
-
B.
Dutch regent
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.
-
C.
member of the Dutch royal family by marriage
A member of the Dutch royal family by marriage is an individual who acquires royal status and associated roles through legally recognized union with a born or reigning member of the Dutch royal house.
-
D.
Dutch noblewoman
A Dutch noblewoman is a female member of the Netherlands' aristocracy, typically holding a hereditary or granted title and associated with historical social status, landownership, and cultural influence.
-
E.
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.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:09 p.m.