Triple
T30481287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | آل سعود |
E775594
|
entity |
| Predicate | تتولى العرش في |
P169781
|
FINISHED |
| Object | المملكة العربية السعودية |
—
|
NE NERFINISHED |
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: المملكة العربية السعودية | Statement: [آل سعود, تتولى العرش في, المملكة العربية السعودية]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: تتولى العرش في Context triple: [آل سعود, تتولى العرش في, المملكة العربية السعودية]
-
A.
tookThroneFollowing
Indicates that one entity assumed or claimed a throne or rulership position directly after another entity, in a succession context.
-
B.
succeededToThroneAs
Indicates that one entity became the new ruler by taking over the throne in a specified role or title from another entity.
-
C.
ascendedToThroneAs
Indicates that an individual assumed royal power and officially became the reigning monarch under a specific title or role.
-
D.
succeededToThroneOf
Indicates that one entity became the next ruler by taking over the throne previously held by another entity.
-
E.
succeededToThrone
Indicates that one entity became the new ruler by taking over the throne previously held by another entity.
- F. None of above. chosen
Provenance (4 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_69f22497341481909c21ba329fadaa6b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f687415610819081818d08f7c79a81 |
completed | May 2, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f7e116c819099aec724e9ef3763 |
completed | May 2, 2026, 10:49 p.m. |
Created at: April 29, 2026, 8:12 p.m.