Triple
T33791999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | يعقوب المنصور الموحدي |
E865954
|
entity |
| Predicate | ثبّت_السلطة_في |
P91036
|
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.
seizedPowerBy
Indicates that one entity took control or authority from another, typically through force, coercion, or other non-consensual means.
-
B.
exerciseOfPower
Indicates the exertion or application of authority, control, or influence by one entity over another or within a given context.
-
C.
subjectOfPower
Indicates that one entity holds authority, control, or influence over another entity.
-
D.
strengthenedOfficeOf
chosen
Indicates that an entity has taken actions or implemented changes that increased the power, authority, or effectiveness of a particular office or official position.
-
E.
securedThroneBy
Indicates that one entity obtained or maintained a throne or rulership position through the actions, support, or intervention of 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.