Triple
T36167667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linda Mary Bonney |
E1046055
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of royalty by marriage |
C11665
|
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 royalty by marriage Context triple: [Linda Mary Bonney, instanceOf, member of royalty by marriage]
-
A.
member of former royal family by marriage
A member of a former royal family by marriage is an individual who has acquired royal family status through wedlock to a person born into a now-deposed or non-reigning royal house.
-
B.
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.
-
C.
member of a royal family
chosen
A member of a royal family is an individual related by blood, marriage, or adoption to a reigning or formerly reigning monarch, typically holding a recognized title, status, or role within the monarchy.
-
D.
spouse of a British royal
A spouse of a British royal is an individual who is married to a member of the British royal family, often undertaking public duties and holding courtesy titles associated with their partner’s rank.
-
E.
member of extended royal family
A member of the extended royal family is an individual related by blood, marriage, or adoption to the reigning monarch or core royal line, but who holds a more distant position in the line of succession and typically fewer official duties.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.