Triple
T1386674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surah Yunus |
E29860
|
entity |
| Predicate | recitedIn |
P9184
|
FINISHED |
| Object | Muslim prayers and worship |
—
|
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 and worship | Statement: [Surah Yunus, recitedIn, Muslim prayers and worship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recitedIn Context triple: [Surah Yunus, recitedIn, Muslim prayers and worship]
-
A.
notRecitedOn
Indicates that a particular text, prayer, or recitation was not performed or spoken on a specified occasion, time, or context.
-
B.
recordedInRelease
Indicates that an audio or media recording is included as part of a specific release (such as an album, single, or edition).
-
C.
narratedTo
Indicates that one entity tells or recounts a story, event, or information directly to another entity as the audience.
-
D.
presentedIn
Indicates that something is shown, displayed, or formally introduced within a particular context, medium, event, or setting.
-
E.
recitationTradition
chosen
Indicates a relationship where a text, work, or content is transmitted or performed according to a particular established style, method, or lineage of recitation.
- 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c33b6e108190b6b2bca4ddd97b6c |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4beffcf808190ab4cd0271257ce63 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.