Triple
T16356434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ndlovukati |
E397191
|
entity |
| Predicate | positionInMonarchy |
P121985
|
FINISHED |
| Object | co-ruler with the King of Eswatini |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: co-ruler with the King of Eswatini | Statement: [Ndlovukati, positionInMonarchy, co-ruler with the King of Eswatini]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInMonarchy Context triple: [Ndlovukati, positionInMonarchy, co-ruler with the King of Eswatini]
-
A.
positionOnMonarchy
Indicates a stance, opinion, or policy position that an entity holds regarding the institution or system of monarchy.
-
B.
positionInRoyalFamily
Indicates the familial rank or role an individual holds within a royal family hierarchy.
-
C.
monarchicRank
Indicates the hierarchical level or status an individual holds within a monarchical system of rule.
-
D.
monarchicalRole
chosen
Indicates that one entity holds or is assigned a specific position, function, or office within a monarchical system of governance.
-
E.
positionInRegalia
Indicates the specific role or rank an individual holds within a formal regalia or ceremonial order.
- F. None of above.
Provenance (3 batches)
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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2facf67e0819089a23ce6f5642fbe |
completed | April 18, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.