Triple
T33946707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quran 54:2 |
E870309
|
entity |
| Predicate | hasTafsirBy |
P75789
|
FINISHED |
| Object | Ibn Kathir |
—
|
NE NERFINISHED |
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: Ibn Kathir | Statement: [Quran 54:2, hasTafsirBy, Ibn Kathir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTafsirBy Context triple: [Quran 54:2, hasTafsirBy, Ibn Kathir]
-
A.
hasExegesisBy
chosen
Indicates that an entity (such as a text or passage) is the subject of an exegesis authored or provided by another entity.
-
B.
hasQuranicEquivalent
Indicates that something has a corresponding or analogous concept, term, or passage found in the Quran.
-
C.
hasVersesBy
Indicates a relationship where a work, such as a song or poem, contains verses authored or written by a specific creator.
-
D.
hasQuranicDescription
Indicates that there exists a description or characterization of the subject that is explicitly given or referenced in the Quran.
-
E.
qiraatTransmittedBy
Indicates that a particular Qur’anic recitation (qirāʾah) is transmitted or narrated through a specific transmitter or chain of transmitters.
- 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f728a345488190bd7e6751b09ac591 |
completed | May 3, 2026, 10:51 a.m. |
| PD | Predicate disambiguation | batch_69f7283ef2608190a7a85d7e7f5332c0 |
completed | May 3, 2026, 10:49 a.m. |
Created at: May 1, 2026, 1:49 a.m.