Triple
T28577187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ProphetsInIslam |
E723273
|
entity |
| Predicate | finalProphet |
P88738
|
FINISHED |
| Object | MuhammadInIslam |
—
|
NE NERFINISHED |
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: MuhammadInIslam | Statement: [ProphetsInIslam, finalProphet, MuhammadInIslam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalProphet Context triple: [ProphetsInIslam, finalProphet, MuhammadInIslam]
-
A.
prophecyMade
Indicates that a prophetic statement or prediction has been declared by one entity concerning a future event or outcome involving another entity.
-
B.
prophetAmong
chosen
Indicates that one entity serves as a prophet within, or in relation to, a particular group, community, or people represented by the other entity.
-
C.
prophecyFulfilled
Indicates that a previously made prophecy has come to pass as foretold.
-
D.
prophecyAccuracy
Indicates how closely a given prophecy’s content or outcome matches the events that actually occur.
-
E.
prophecyKnownAs
Indicates that a particular prophecy is referred to or recognized by a specific name or title.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 28, 2026, 4:13 a.m.