Triple
T14284598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Qari'atu |
E354135
|
entity |
| Predicate | quranicSurahType |
P112042
|
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: [Al-Qari'atu, quranicSurahType, Meccan surah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: quranicSurahType Context triple: [Al-Qari'atu, quranicSurahType, Meccan surah]
-
A.
quranicChapterType
chosen
Indicates the classification relationship that specifies what type or category a given Quranic chapter belongs to.
-
B.
quranicSurah
Indicates that one entity is a chapter (surah) of the Quran associated with or identified by the other entity.
-
C.
includeSurah
Indicates that one entity (such as a collection, book, or document) contains or incorporates a specific Surah as part of its contents.
-
D.
quranicSurahMention
Indicates that a specific Quranic surah is mentioned, referenced, or cited in relation to another entity or context.
-
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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de697d9fd08190b0cd7a6a6737ba03 |
completed | April 14, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:10 a.m.