Triple
T9235005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sudairi Seven |
E221913
|
entity |
| Predicate | internalRole |
P40371
|
FINISHED |
| Object | power center within House of Saud |
—
|
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: power center within House of Saud | Statement: [Sudairi Seven, internalRole, power center within House of Saud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internalRole Context triple: [Sudairi Seven, internalRole, power center within House of Saud]
-
A.
secretRole
Indicates that an entity holds a role or function that is intentionally hidden or not publicly disclosed within a given context.
-
B.
externalRole
Indicates that an entity holds a role or position in relation to another entity or organization that is outside its primary or internal structure.
-
C.
intraPartyRole
Indicates a role or function that an entity holds within a specific political party or internal party structure.
-
D.
companyInternal
Indicates that the relationship or action occurs within the same company or is restricted to internal company context.
-
E.
unitRole
chosen
Indicates the functional role or purpose that a unit serves within a larger system or context.
- 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_69ca83ed628c8190bc02d641e57f097f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccee1cca0c8190bf587f54236c9e45 |
completed | April 1, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4765648190aa9445c4a22dc471 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:29 p.m.