Triple
T11496961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fay (non-battle war gains) |
E272558
|
entity |
| Predicate | primaryQuranicSourceVerse |
P76649
|
FINISHED |
| Object | Quran 59:6 |
—
|
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 59:6 | Statement: [Fay (non-battle war gains), primaryQuranicSourceVerse, Quran 59:6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryQuranicSourceVerse Context triple: [Fay (non-battle war gains), primaryQuranicSourceVerse, Quran 59:6]
-
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.
basedOnQuranVerse
chosen
Indicates that something is derived from, inspired by, or directly references a specific verse of the Quran.
-
C.
hasQuranicVerseReference
Indicates that an entity is associated with, or refers to, a specific verse or verses from the Quran.
-
D.
quranicSurahMention
Indicates that a specific Quranic surah is mentioned, referenced, or cited in relation to another entity or context.
-
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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85de183f08190abfa36eaabc61dc6 |
completed | April 10, 2026, 2:18 a.m. |
| PD | Predicate disambiguation | batch_69d808736c5c8190899b5b3b2e797f65 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.