Triple
T36883313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Lalla Asma of Morocco |
E911540
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Moroccan royal family |
C65932
|
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 Moroccan royal family Context triple: [Princess Lalla Asma of Morocco, instanceOf, member of the Moroccan royal family]
-
A.
member of the House of Saud
A member of the House of Saud is an individual belonging by blood or marriage to the ruling royal family of Saudi Arabia, often holding political, economic, or religious influence within the kingdom.
-
B.
member of the Al Maktoum family
A member of the Al Maktoum family is an individual belonging to the ruling royal dynasty of Dubai, part of the United Arab Emirates, known for its political leadership, wealth, and influence in the region.
-
C.
member of the Al Khalifa dynasty
A member of the Al Khalifa dynasty is an individual belonging by birth or marriage to the ruling royal family of Bahrain, historically and presently central to the country’s political authority and governance.
-
D.
member of Al Sheikh family
A member of Al Sheikh family is an individual belonging by blood or legal relation to the Al Sheikh lineage, sharing its heritage, name, and familial responsibilities.
-
E.
Moroccan royal consort
A Moroccan royal consort is the spouse of a reigning or former Moroccan monarch who supports the sovereign’s public role and may undertake ceremonial, charitable, and representational duties within the royal household and state.
- 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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.