Triple
T1031625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Faisal bin Hussein |
E22264
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Jordanian 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 Jordanian royal family Context triple: [Prince Faisal bin Hussein, instanceOf, member of the Jordanian royal family]
-
A.
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.
-
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.
Scottish prince
A Scottish prince is a male royal family member of Scotland, typically in the line of succession to the Scottish throne and bearing titles and duties associated with Scottish nobility and governance.
-
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.
royal prince
A royal prince is a male member of a monarchy’s ruling family, typically in the line of succession to the throne and bearing ceremonial, diplomatic, and sometimes administrative duties.
- 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_69a493d848848190aed4011b34b2e8d3 |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:41 p.m.