Triple
T2899520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mohamed bin Zayed Al Nahyan |
E62621
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of a royal family |
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 family Context triple: [Mohamed bin Zayed Al Nahyan, instanceOf, member of a royal family]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
British princess
A British princess is a female member of the British royal family, typically bearing the title by birth or marriage and undertaking ceremonial, charitable, and representational duties on behalf of the monarchy.
-
E.
member of the House of Stuart
A member of the House of Stuart is an individual belonging by birth or legitimate descent to the royal dynasty that ruled Scotland and later England, Great Britain, and Ireland between the late 14th and early 18th centuries.
- F. None of above. chosen
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_69ab4c3e070c8190b78d3d2c005876dd |
completed | March 6, 2026, 9:50 p.m. |
Created at: March 6, 2026, 10:10 p.m.