Triple
T31951866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qur’an 46:27 |
E815800
|
entity |
| Predicate | contextInSurah |
P71343
|
FINISHED |
| Object | part of warnings to the people of Mecca |
—
|
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: part of warnings to the people of Mecca | Statement: [Qur’an 46:27, contextInSurah, part of warnings to the people of Mecca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contextInSurah Context triple: [Qur’an 46:27, contextInSurah, part of warnings to the people of Mecca]
-
A.
quranicContext
Indicates that something is situated within, derived from, or directly related to the textual, historical, or thematic context of the Quran.
-
B.
commandInSurah
Indicates that a particular command or directive appears within a specified surah (chapter) of the Quran.
-
C.
occursInSurah
chosen
Indicates that something (such as a verse, concept, or event) takes place within or is contained in a specific surah.
-
D.
subjectOfSurah
Indicates that an entity is the main topic, theme, or focus discussed within a specific surah (chapter) of the Quran.
-
E.
quranSection
Indicates that one entity is a section, passage, or subdivided part of the Quran associated with another 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: May 1, 2026, 12:07 a.m.