Triple
T12790712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahdism |
E305750
|
entity |
| Predicate | expectsEvent |
P106933
|
FINISHED |
| Object | emergence of a just ruler at the end of times |
—
|
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: emergence of a just ruler at the end of times | Statement: [Mahdism, expectsEvent, emergence of a just ruler at the end of times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expectsEvent Context triple: [Mahdism, expectsEvent, emergence of a just ruler at the end of times]
-
A.
attendsTo
Indicates that one entity directs care, attention, or service toward another entity or task.
-
B.
eventBefore
Indicates that one event occurs earlier in time than another event.
-
C.
exposesEvent
Indicates that one entity makes an event available or visible for use, handling, or observation by another entity or system.
-
D.
eventoDesencadenante
Indicates that one event serves as the trigger or initiating cause for another event or process.
-
E.
coversEvent
Indicates that one event includes, spans, or encompasses the time period or occurrence of another event.
- F. None of above. chosen
Provenance (4 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e6b55248190ab938e69eb263612 |
completed | April 10, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:30 p.m.