Triple
T31966585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Saudi Arabia |
E816194
|
entity |
| Predicate | mayHoldRoleIn |
P143289
|
FINISHED |
| Object | political affairs of Saudi Arabia |
—
|
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: political affairs of Saudi Arabia | Statement: [Prince of Saudi Arabia, mayHoldRoleIn, political affairs of Saudi Arabia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayHoldRoleIn Context triple: [Prince of Saudi Arabia, mayHoldRoleIn, political affairs of Saudi Arabia]
-
A.
mayHaveRole
chosen
Indicates that an entity is permitted or eligible to hold or perform a specified role.
-
B.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
-
C.
mayHoldTitleOf
Indicates that an entity is permitted or eligible to possess or bear a particular title.
-
D.
mayHoldQualification
Indicates that an entity is permitted or able to possess a particular qualification, certification, or credential.
-
E.
mayGrant
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
- 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b2eca2c481909f1ebb3d23d45c17 |
completed | May 3, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:09 a.m.