Triple
T6595690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sophie, Hereditary Princess of Liechtenstein |
E148469
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of a royal house |
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 a royal house Context triple: [Sophie, Hereditary Princess of Liechtenstein, instanceOf, member of a royal house]
-
A.
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.
-
B.
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.
-
C.
British royal
A British royal is a member of the United Kingdom’s monarchy, typically born or married into the royal family, who embodies and represents national tradition, continuity, and ceremonial leadership.
-
D.
member of the House of Bourbon
A member of the House of Bourbon is an individual belonging by birth or legitimate descent to the historic European royal dynasty that ruled or influenced several kingdoms, including France, Spain, and Naples.
-
E.
royal house
A royal house is a dynastic family line that holds or has held a hereditary monarchy, encompassing its members, titles, traditions, and political influence over time.
- 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_69c687e7b8688190811ffee72e096468 |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 1:55 p.m.