Triple
T8939294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luqman |
E212856
|
entity |
| Predicate | verseRangeInSurahLuqman |
P27216
|
FINISHED |
| Object | Qur'an 31:12-19 |
—
|
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: Qur'an 31:12-19 | Statement: [Luqman, verseRangeInSurahLuqman, Qur'an 31:12-19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verseRangeInSurahLuqman Context triple: [Luqman, verseRangeInSurahLuqman, Qur'an 31:12-19]
-
A.
hasVerseRange
chosen
Indicates a relationship where a text or passage is associated with a specific contiguous range of verses it spans.
-
B.
commandInSurah
Indicates that a particular command or directive appears within a specified surah (chapter) of the Quran.
-
C.
occursInSurah
Indicates that something (such as a verse, concept, or event) takes place within or is contained in a specific surah.
-
D.
quranSection
Indicates that one entity is a section, passage, or subdivided part of the Quran associated with another entity.
-
E.
quranicSurahMention
Indicates that a specific Quranic surah is mentioned, referenced, or cited in relation to another entity or context.
- 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_69ca839694c88190b324ffeb43d23b08 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66b7484481909e0d7610552f5386 |
completed | April 1, 2026, 12:28 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:58 p.m.