Triple
T15899638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quran 112:1-4 |
E385549
|
entity |
| Predicate | locatedInSurahNumber |
P71343
|
FINISHED |
| Object | 112 |
—
|
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: 112 | Statement: [Quran 112:1-4, locatedInSurahNumber, 112]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInSurahNumber Context triple: [Quran 112:1-4, locatedInSurahNumber, 112]
-
A.
occursInSurah
chosen
Indicates that something (such as a verse, concept, or event) takes place within or is contained in a specific surah.
-
B.
commandInSurah
Indicates that a particular command or directive appears within a specified surah (chapter) of the Quran.
-
C.
quranSurahNumber
Indicates the numerical position or identifier assigned to a specific surah (chapter) within the Quran.
-
D.
foundInMushaf
Indicates that something (such as a verse, phrase, or reading) is present and recorded in the written text of the Mushaf (the compiled Qur’anic codex).
-
E.
quranManzil
Indicates a relationship where a portion of the Quran is assigned or associated as a specific “manzil” (section) for recitation or division purposes.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142ca3b208190946c3aa4c1e6087c |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.