Triple
T621584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shia Islam |
E14524
|
entity |
| Predicate | expects |
P786
|
FINISHED |
| Object | return of the Mahdi |
—
|
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: return of the Mahdi | Statement: [Shia Islam, expects, return of the Mahdi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expects Context triple: [Shia Islam, expects, return of the Mahdi]
-
A.
anticipates
chosen
Indicates that one entity expects or predicts a future event, action, or state involving another entity before it actually occurs.
-
B.
assumes
Indicates that one entity takes on, accepts, or presumes a role, responsibility, state, or fact regarding another entity or situation.
-
C.
holdsFor
Indicates that a particular relationship or condition remains true over a specified interval or duration of time.
-
D.
expresses
Indicates that one entity conveys, communicates, or articulates a thought, feeling, or idea through another medium or form.
-
E.
ensures
Indicates that one entity guarantees or makes certain that a particular condition, outcome, or state holds for another entity or situation.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e3e5d80819096e72e11b533f931 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfe9bc081909a01b4b3b48f03b7 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.