Triple
T24294778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qibla (toward the Kaaba) |
E605927
|
entity |
| Predicate | quranicVersesReference |
P93494
|
FINISHED |
| Object | Quran 2:142 |
—
|
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: Quran 2:142 | Statement: [Qibla (toward the Kaaba), quranicVersesReference, Quran 2:142]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: quranicVersesReference Context triple: [Qibla (toward the Kaaba), quranicVersesReference, Quran 2:142]
-
A.
quranicVerse
Indicates that a given text segment is a verse from the Quran and encodes the relationship between that verse and its source scripture.
-
B.
quranicSurahMention
Indicates that a specific Quranic surah is mentioned, referenced, or cited in relation to another entity or context.
-
C.
quranSection
Indicates that one entity is a section, passage, or subdivided part of the Quran associated with another entity.
-
D.
quranicPhrase
Indicates that one entity is a phrase or expression that appears in, or is directly derived from, the Quran.
-
E.
hasQuranicVerseReference
chosen
Indicates that an entity is associated with, or refers to, a specific verse or verses from 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f291593c0881908a6827f0d8899fe6 |
completed | April 29, 2026, 11:16 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 12:09 a.m.