Triple
T30481307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | آل سعود |
E775594
|
entity |
| Predicate | نظام انتقال الحكم |
P88791
|
FINISHED |
| Object | الملكية الوراثية في أبناء الملك المؤسس وذريتهم |
—
|
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: الملكية الوراثية في أبناء الملك المؤسس وذريتهم | Statement: [آل سعود, نظام انتقال الحكم, الملكية الوراثية في أبناء الملك المؤسس وذريتهم]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: نظام انتقال الحكم Context triple: [آل سعود, نظام انتقال الحكم, الملكية الوراثية في أبناء الملك المؤسس وذريتهم]
-
A.
نظامالحكم
Indicates the type or structure of governance or political system under which an entity is ruled.
-
B.
laterPoliticalSystemUnderRule
Indicates that one political system came under the rule or authority of another political system at a later point in time.
-
C.
تاريخ تولي الحكم
Indicates the date on which an individual assumed power or began their rule.
-
D.
governedSuccessionOf
chosen
Indicates a succession relationship in which one entity follows another under an established governing rule, law, or authority.
-
E.
يحكمها
Indicates that an entity governs, rules, or exercises authority over 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_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_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:12 p.m.