Triple
T17373021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederik André Henrik Christian |
E422363
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Danish royal family |
C15721
|
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 the Danish royal family Context triple: [Frederik André Henrik Christian, instanceOf, member of the Danish royal family]
-
A.
member of a royal family
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.
-
B.
member of the English royal family
A member of the English royal family is an individual related by blood or legally recognized ties to the reigning monarch, holding a formal or ceremonial position within the United Kingdom’s constitutional monarchy.
-
C.
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.
-
D.
Danish royal
chosen
A Danish royal is a member of Denmark’s monarchy, belonging to the Danish royal family by birth or marriage and typically engaged in ceremonial, constitutional, and representational duties for the Danish state.
-
E.
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.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:44 a.m.