Triple
T1127244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fatimid Caliphate |
E24746
|
entity |
| Predicate | legitimacyClaim |
P4867
|
FINISHED |
| Object | descent from Ali ibn Abi Talib |
—
|
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: descent from Ali ibn Abi Talib | Statement: [Fatimid Caliphate, legitimacyClaim, descent from Ali ibn Abi Talib]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legitimacyClaim Context triple: [Fatimid Caliphate, legitimacyClaim, descent from Ali ibn Abi Talib]
-
A.
mainClaim
Indicates that one statement is presented as the central or primary assertion being made about a topic.
-
B.
legitimizedBy
Indicates that something gains legal, formal, or social validity as a result of the authority, action, or endorsement of another entity.
-
C.
lineageClaim
chosen
Indicates a claim or assertion that one entity is descended from, or belongs to the ancestral line of, another entity.
-
D.
historicalClaim
Indicates that an entity asserts or presents a statement about past events or conditions as a matter of historical fact.
-
E.
definesClaim
Indicates that one entity specifies or establishes the meaning, scope, or content of another entity’s claim.
- 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_69a4940712c88190aa244f3fc6070a65 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb48de2081909a0dce005b1c9df1 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.