Triple
T26062175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mother of the Book |
E657288
|
entity |
| Predicate | associatedSurahName |
P75743
|
FINISHED |
| Object | Al-Fatiha |
—
|
NE NERFINISHED |
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: Al-Fatiha | Statement: [Mother of the Book, associatedSurahName, Al-Fatiha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedSurahName Context triple: [Mother of the Book, associatedSurahName, Al-Fatiha]
-
A.
subjectOfSurah
Indicates that an entity is the main topic, theme, or focus discussed within a specific surah (chapter) of the Quran.
-
B.
followsSurah
Indicates that one surah directly comes after or is ordered immediately following another surah in a specified sequence.
-
C.
quranSurahAlternateName
chosen
Indicates that a particular name is an alternate or secondary title used to refer to a specific surah of the Quran.
-
D.
quranicDerivative
Indicates that one entity is a linguistic form or term derived from, based on, or morphologically related to a word or concept found in the Quran.
-
E.
quranicSurah
Indicates that one entity is a chapter (surah) of the Quran associated with or identified by the other entity.
- 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_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
Created at: April 26, 2026, 7:18 p.m.