Triple
T20821901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barelvi movement |
E512594
|
entity |
| Predicate | viewsProphetMuhammadAs |
P141961
|
FINISHED |
| Object | intercessor |
—
|
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: intercessor | Statement: [Barelvi movement, viewsProphetMuhammadAs, intercessor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewsProphetMuhammadAs Context triple: [Barelvi movement, viewsProphetMuhammadAs, intercessor]
-
A.
viewOnProphethood
Indicates a subject’s stance or belief regarding the concept, status, or legitimacy of prophethood.
-
B.
viewOnImams
Indicates the stance, opinion, or doctrinal position that one entity holds regarding the role, status, or authority of Imams.
-
C.
regardsAsFinalProphet
Indicates that one entity believes or treats another entity as the ultimate and last prophet, after whom no further prophets will come.
-
D.
regardsAsOnlyProphetAfterMoses
Indicates that one entity considers another entity to be the sole legitimate prophet following Moses.
-
E.
roleInIslamicHistory
Indicates the specific function, status, or contribution an entity has within the context of Islamic historical events, periods, or developments.
- 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_69e0b4ce39108190a6e8e5df4f1c8dc5 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2fb49148190bdad1b51e7dac43a |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:41 p.m.