Triple
T7735969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quran 15:44 |
E175381
|
entity |
| Predicate | surahType |
P30310
|
FINISHED |
| Object | Meccan surah |
—
|
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: Meccan surah | Statement: [Quran 15:44, surahType, Meccan surah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surahType Context triple: [Quran 15:44, surahType, Meccan surah]
-
A.
quranicSurah
Indicates that one entity is a chapter (surah) of the Quran associated with or identified by the other entity.
-
B.
isMeccanSurah
chosen
Indicates that a given surah (chapter of the Qur’an) was revealed in Mecca (i.e., is classified as a Meccan surah) rather than in Medina.
-
C.
followsSurah
Indicates that one surah directly comes after or is ordered immediately following another surah in a specified sequence.
-
D.
commandInSurah
Indicates that a particular command or directive appears within a specified surah (chapter) of the Quran.
-
E.
quranSurahAlternateName
Indicates that a particular name is an alternate or secondary title used to refer to a specific surah of the Quran.
- 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_69c6995f9c60819092e386192bd63c6f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c7016c4a748190a7012030edaefcee |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:06 p.m.