Triple
T15679064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Occultation |
E377523
|
entity |
| Predicate | describesStateOf |
P264
|
FINISHED |
| Object | Muhammad al-Mahdi being alive but hidden |
—
|
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: Muhammad al-Mahdi being alive but hidden | Statement: [Occultation, describesStateOf, Muhammad al-Mahdi being alive but hidden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesStateOf Context triple: [Occultation, describesStateOf, Muhammad al-Mahdi being alive but hidden]
-
A.
portraysState
Indicates that one entity visually or symbolically represents or depicts the condition, status, or situation of another entity.
-
B.
describes
chosen
Indicates that one entity provides an explanation, representation, or account of another entity or concept.
-
C.
inState
Indicates that an entity is currently located within or belongs to a particular state or condition.
-
D.
stateOfActivity
Indicates the current condition, phase, or status that an activity is in at a given time.
-
E.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f2f1640819086efd5a73bb9734a |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:16 a.m.