Triple
T10190978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bay‘at al-Ridwan |
E238031
|
entity |
| Predicate | referencedInQuranVerse |
P76649
|
FINISHED |
| Object | Qur’an 48:18 |
—
|
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 48:18 | Statement: [Bay‘at al-Ridwan, referencedInQuranVerse, Qur’an 48:18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referencedInQuranVerse Context triple: [Bay‘at al-Ridwan, referencedInQuranVerse, Qur’an 48:18]
-
A.
basedOnQuranVerse
chosen
Indicates that something is derived from, inspired by, or directly references a specific verse of the Quran.
-
B.
groupedWithInQuran
Indicates that two or more entities are mentioned together or treated as a unit within the same grouping or context in the Quran.
-
C.
describedInHadithAs
Indicates that something is mentioned, characterized, or narrated within a hadith text.
-
D.
quranicPhrase
Indicates that one entity is a phrase or expression that appears in, or is directly derived from, the Quran.
-
E.
knownInIslamAs
Indicates that an entity is referred to by a particular name, title, or designation specifically within the context of Islam or Islamic tradition.
- 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_69ca84de1b208190bf17bb305b002605 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded7eb1148190a2d175163685e233 |
completed | April 2, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69cd7c8477648190bc55c56aeec507d3 |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:13 p.m.