Triple
T3443601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surah Al-Fil |
E72621
|
entity |
| Predicate | memorizationStatus |
P14346
|
FINISHED |
| Object | Commonly memorized by Muslim children |
—
|
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: Commonly memorized by Muslim children | Statement: [Surah Al-Fil, memorizationStatus, Commonly memorized by Muslim children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memorizationStatus Context triple: [Surah Al-Fil, memorizationStatus, Commonly memorized by Muslim children]
-
A.
memorizationPractice
Indicates engaging in activities or exercises specifically intended to commit information to memory or strengthen recall.
-
B.
memorizedBy
chosen
Indicates that some content, information, or material has been learned and retained in memory by a particular entity.
-
C.
rememberedFor
Indicates that one entity is known or recognized primarily because of, or in association with, another entity or achievement.
-
D.
memory
Indicates that an entity retains, recalls, or is associated with stored information or past experiences.
-
E.
hasUserMemory
Indicates that an entity maintains or is associated with stored information about a specific user.
- 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_69ad85b05c848190b7a28ceec2bd7b74 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adba2a605c8190a0eafdf6f25b1e38 |
completed | March 8, 2026, 6:04 p.m. |
| PD | Predicate disambiguation | batch_69adae0255b48190a9069f7871c7a012 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.