Triple
T23429294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Walid ibn Uqba |
E563280
|
entity |
| Predicate | associatedQuranVerse |
P114904
|
FINISHED |
| Object | Qurʾan 49: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: Qurʾan 49:6 | Statement: [al-Walid ibn Uqba, associatedQuranVerse, Qurʾan 49:6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedQuranVerse Context triple: [al-Walid ibn Uqba, associatedQuranVerse, Qurʾan 49: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.
associatedWithVerse
chosen
Indicates a relationship where something is linked or connected to a specific verse, typically in a text or scripture.
-
C.
hasQuranicEquivalent
Indicates that something has a corresponding or analogous concept, term, or passage found in the Quran.
-
D.
basedOnQuranVerse
Indicates that something is derived from, inspired by, or directly references a specific verse of the Quran.
-
E.
groupedWithInQuran
Indicates that two or more entities are mentioned together or treated as a unit within the same grouping or context in 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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a54ba29881909945690496f28d65 |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:48 p.m.