Triple
T31955198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qur’an 46:29 |
E815885
|
entity |
| Predicate | surahClassification |
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: [Qur’an 46:29, surahClassification, Meccan surah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surahClassification Context triple: [Qur’an 46:29, surahClassification, Meccan surah]
-
A.
quranicSurah
Indicates that one entity is a chapter (surah) of the Quran associated with or identified by the other entity.
-
B.
subjectOfSurah
Indicates that an entity is the main topic, theme, or focus discussed within a specific surah (chapter) of the Quran.
-
C.
surahApproximateOrderOfRevelation
Indicates the approximate chronological order in which a given surah was revealed relative to other surahs.
-
D.
includeSurah
Indicates that one entity (such as a collection, book, or document) contains or incorporates a specific Surah as part of its contents.
-
E.
quranicChapterType
chosen
Indicates the classification relationship that specifies what type or category a given Quranic chapter belongs to.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b2ae50e08190b0756dfe533618ea |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:08 a.m.