Triple
T21894364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yaghuth |
E540636
|
entity |
| Predicate | mentionedInQuranVerse |
P93494
|
FINISHED |
| Object | Quran 71:23 |
—
|
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 71:23 | Statement: [Yaghuth, mentionedInQuranVerse, Quran 71:23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionedInQuranVerse Context triple: [Yaghuth, mentionedInQuranVerse, Quran 71:23]
-
A.
hasQuranicVerseReference
chosen
Indicates that an entity is associated with, or refers to, a specific verse or verses from the Quran.
-
B.
basedOnQuranVerse
Indicates that something is derived from, inspired by, or directly references a specific verse of the Quran.
-
C.
quranicSurahMention
Indicates that a specific Quranic surah is mentioned, referenced, or cited in relation to another entity or context.
-
D.
ذُكر_في
Indicates that an entity is mentioned or referenced within another entity, such as a text, document, or source.
-
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_69e0c47a95908190ae3e19b716accb3d |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f11fc539708190a42f202e7404a213 |
completed | April 28, 2026, 8:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:07 p.m.