Triple
T2382413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surah Muhammad |
E46338
|
entity |
| Predicate | isRecitedIn |
P33123
|
FINISHED |
| Object | Muslim prayers |
—
|
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: Muslim prayers | Statement: [Surah Muhammad, isRecitedIn, Muslim prayers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRecitedIn Context triple: [Surah Muhammad, isRecitedIn, Muslim prayers]
-
A.
recitedOnOccasion
chosen
Indicates that something (typically a text, speech, or performance) was recited during or in connection with a specific occasion or event.
-
B.
notRecitedOn
Indicates that a particular text, prayer, or recitation was not performed or spoken on a specified occasion, time, or context.
-
C.
narratedHadith
Indicates that one entity transmitted or reported a hadith (a prophetic narration) from or about another entity.
-
D.
recognizesScripturesFrom
Indicates that one entity acknowledges or accepts certain scriptures as authoritative or valid based on another entity as their source or origin.
-
E.
narratedTo
Indicates that one entity tells or recounts a story, event, or information directly to another entity as the audience.
- 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_69a88a1554a48190a0180682bcf099be |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc7b98c988190abdb4fe51bf65bde |
completed | March 7, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69abc59f73f08190924a36d7d475d8f4 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.