Triple
T30359777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walid ibn al-Mughirah |
E772246
|
entity |
| Predicate | describedQuranAs |
P71466
|
FINISHED |
| Object | magic |
—
|
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: magic | Statement: [Walid ibn al-Mughirah, describedQuranAs, magic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedQuranAs Context triple: [Walid ibn al-Mughirah, describedQuranAs, magic]
-
A.
quranicDescription
Indicates that one entity is described, characterized, or referenced within the text of the Quran in relation to another entity.
-
B.
hasQuranicDescription
chosen
Indicates that there exists a description or characterization of the subject that is explicitly given or referenced in the Quran.
-
C.
quranicContext
Indicates that something is situated within, derived from, or directly related to the textual, historical, or thematic context of the Quran.
-
D.
describedInHadithAs
Indicates that something is mentioned, characterized, or narrated within a hadith text.
-
E.
regardedAsScriptureBy
Indicates that something is considered to be sacred scripture or canonical religious text by a particular person, group, or 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 29, 2026, 7:57 p.m.