Triple
T26062107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mushaf |
E657286
|
entity |
| Predicate | hasReadingAids |
P39027
|
FINISHED |
| Object | Vowel marks |
—
|
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: Vowel marks | Statement: [Mushaf, hasReadingAids, Vowel marks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReadingAids Context triple: [Mushaf, hasReadingAids, Vowel marks]
-
A.
readingAid
chosen
Indicates that one entity assists or facilitates another entity’s ability to read or engage in reading activities.
-
B.
hasDyslexia
Indicates that an entity experiences dyslexia, a learning difficulty affecting reading, writing, or spelling abilities.
-
C.
containsReading
Indicates that one entity includes or encompasses a particular reading (such as a measurement, value, or interpretation) within it.
-
D.
hasReading
Indicates that an entity is associated with a particular reading, such as a measured value, interpretation, or recorded observation.
-
E.
accessibilityFeatures
Indicates the specific tools, settings, or design elements provided to make something usable or understandable for people with disabilities or diverse access needs.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: April 26, 2026, 7:18 p.m.