Triple
T6082450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Astrid of Norway |
E135555
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Norwegian royal family |
C7359
|
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 Norwegian royal family Context triple: [Princess Astrid of Norway, instanceOf, member of the Norwegian royal family]
-
A.
Norwegian royal
chosen
A Norwegian royal is a member of Norway’s reigning monarchy, belonging to the royal family and holding ceremonial, constitutional, and representational roles within the Norwegian state.
-
B.
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.
-
C.
Danish royal
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.
-
D.
member of the Japanese imperial family
A member of the Japanese imperial family is an individual related by blood or adoption to the Emperor of Japan, holding a formal status defined by the Imperial Household Law and participating in ceremonial, cultural, and representational duties of the monarchy.
-
E.
Swedish royal
A Swedish royal is a member of Sweden’s monarchy, belonging to the royal family by birth or marriage and often performing ceremonial, diplomatic, and representative duties for the nation.
- 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_69c0087ad31c8190ab936e0ff28614b6 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:11 p.m.