Triple
T26062111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mushaf |
E657286
|
entity |
| Predicate | isMemorizedFromBy |
P159906
|
FINISHED |
| Object | Huffaz (memorizers of Qur’an) |
—
|
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: Huffaz (memorizers of Qur’an) | Statement: [Mushaf, isMemorizedFromBy, Huffaz (memorizers of Qur’an)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMemorizedFromBy Context triple: [Mushaf, isMemorizedFromBy, Huffaz (memorizers of Qur’an)]
-
A.
memorizedBy
Indicates that some content, information, or material has been learned and retained in memory by a particular entity.
-
B.
isMemorizedFor
Indicates that something has been committed to memory specifically for a particular purpose, context, or entity.
-
C.
isMemorizedOrally
Indicates that the information, content, or material is retained and transmitted through oral memorization rather than written or recorded forms.
-
D.
rememberedThrough
Indicates that one entity is remembered, commemorated, or kept in memory by means of, or through the influence of, another entity or medium.
-
E.
rememberedFor
Indicates that one entity is known or recognized primarily because of, or in association with, another entity or achievement.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f606941410819098a15b288273c3e1 |
completed | May 2, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 7:18 p.m.