Triple
T1317010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | As-Samad |
E28126
|
entity |
| Predicate | recitedFor |
P9184
|
FINISHED |
| Object | Seeking reliance on Allah alone |
—
|
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: Seeking reliance on Allah alone | Statement: [As-Samad, recitedFor, Seeking reliance on Allah alone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recitedFor Context triple: [As-Samad, recitedFor, Seeking reliance on Allah alone]
-
A.
notRecitedOn
Indicates that a particular text, prayer, or recitation was not performed or spoken on a specified occasion, time, or context.
-
B.
recordedFor
Indicates that something has been documented, captured, or logged on behalf of or in association with a particular entity or context.
-
C.
narratedTo
Indicates that one entity tells or recounts a story, event, or information directly to another entity as the audience.
-
D.
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.
-
E.
presentedFor
Indicates that one entity was formally offered, submitted, or shown to another entity for consideration, review, or action.
- 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_69a498532c3481909223b74af2e578df |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c175079481909077cf11ed72d6fa |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beebcb348190964bd7215811942c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.