Triple
T20499670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ملكة الأردن |
E503266
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | منصب في النظام الملكي الأردني |
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: منصب في النظام الملكي الأردني Context triple: [ملكة الأردن, instanceOf, منصب في النظام الملكي الأردني]
-
A.
Jordanian government position
A Jordanian government position is an official role within the Hashemite Kingdom of Jordan’s public sector responsible for executing state functions, implementing national policies, and serving citizens under the country’s constitutional and administrative framework.
-
B.
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.
-
C.
Jordanian government body
A Jordanian government body is an official public institution established by the Hashemite Kingdom of Jordan to implement laws, formulate and execute policies, and provide administrative or regulatory services within its designated domain.
-
D.
Governorate of Jordan
A Governorate of Jordan is a primary administrative division of the country, governed by an appointed governor and responsible for local administration, public services, and regional development within its defined geographic area.
-
E.
regent position
A regent position is a temporary governing role held by an individual appointed to rule on behalf of a monarch or leader who is unable to fulfill their duties due to minority, absence, or incapacity.
- 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_69e0b4b1e52c8190894281cf7e3283ab |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:35 a.m.