Triple
T5997618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iman bint Hussein |
E133512
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Hashemite royal family |
C4059
|
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 Hashemite royal family Context triple: [Iman bint Hussein, instanceOf, member of the Hashemite royal family]
-
A.
member of the Hussein family
A member of the Hussein family is an individual who belongs by blood, marriage, or adoption to the familial lineage identified by the Hussein surname and its shared heritage, responsibilities, and relationships.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
Jordanian royal
chosen
A Jordanian royal is a member of Jordan’s ruling Hashemite family, holding hereditary status, ceremonial and political roles, and representing the kingdom domestically and internationally.
- 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_69c00870ddbc81909880fa3864f4f38d |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:05 p.m.