Triple
T8992234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahdist Ansar forces |
E214817
|
entity |
| Predicate | basedOnBeliefIn |
P38879
|
FINISHED |
| Object | Mahdism |
—
|
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: Mahdism | Statement: [Mahdist Ansar forces, basedOnBeliefIn, Mahdism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnBeliefIn Context triple: [Mahdist Ansar forces, basedOnBeliefIn, Mahdism]
-
A.
basedOnBelief
chosen
Indicates that one entity’s action, decision, or assertion is grounded in, motivated by, or derived from a particular belief held by that entity.
-
B.
originBelief
Indicates a belief or assumption about where something or someone comes from or originated.
-
C.
believedBy
Indicates that a particular proposition, statement, or entity is held to be true or accepted as real by a specified believer.
-
D.
hasCentralBelief
Indicates that a particular belief is a core or foundational belief within an entity’s overall belief system.
-
E.
beliefEncouragedBy
Indicates that one entity’s belief is supported, strengthened, or promoted as a result of influence, actions, or encouragement from 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_69ca83a05c608190bdfdbdb25e994b39 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6876583081909d936dc3c3152587 |
completed | April 1, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69cc5edba0f88190b97401636a076d7a |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:04 p.m.