Triple
T34312984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Mahdi |
E880502
|
entity |
| Predicate | usedForLegitimacyOf |
P39443
|
FINISHED |
| Object | Almohad rule |
—
|
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: Almohad rule | Statement: [al-Mahdi, usedForLegitimacyOf, Almohad rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForLegitimacyOf Context triple: [al-Mahdi, usedForLegitimacyOf, Almohad rule]
-
A.
helpedLegitimize
Indicates that one entity’s actions or support contributed to making another entity appear more credible, acceptable, or officially recognized.
-
B.
legitimizedBy
Indicates that something gains legal, formal, or social validity as a result of the authority, action, or endorsement of another entity.
-
C.
authorityLegitimacyBasis
chosen
Indicates the foundational source or justification that makes an authority’s power or right to rule recognized as valid or legitimate.
-
D.
claimedLegitimacyOver
Indicates that one entity has asserted or declared its rightful authority, validity, or dominance over another entity.
-
E.
justificationUsedBy
Indicates that a particular justification is employed or relied upon by a given entity (such as a person, system, or decision).
- 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_69f349b8bb6c8190ad12a7957a574f04 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 1, 2026, 1:57 a.m.