Triple
T1974441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surah Fussilat |
E42876
|
entity |
| Predicate | hasProstrationVerseNumber |
P27929
|
FINISHED |
| Object | 38 |
—
|
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: 38 | Statement: [Surah Fussilat, hasProstrationVerseNumber, 38]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProstrationVerseNumber Context triple: [Surah Fussilat, hasProstrationVerseNumber, 38]
-
A.
containsProstrationVerse
Indicates that a text or passage includes at least one verse that requires or is associated with performing a prostration.
-
B.
sajdahVerseNumber
chosen
Indicates the verse number in a chapter at which a prostration (sajdah) is prescribed or occurs.
-
C.
isMeccanSurah
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.
-
D.
quranicSurahMention
Indicates that a specific Quranic surah is mentioned, referenced, or cited in relation to another entity or context.
-
E.
quranicStatus
Indicates the status or classification of something in relation to its recognition, treatment, or role within 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_69a8871289048190b00b0d7744b7b2b1 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3f6c4208190a41e02733faed8df |
completed | March 7, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69abaff9a09c8190a81fa13f4b85bc79 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.