Triple
T31685260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qur’an 46:13 |
E808640
|
entity |
| Predicate | exegesisField |
P102848
|
FINISHED |
| Object | tafsir literature |
—
|
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: tafsir literature | Statement: [Qur’an 46:13, exegesisField, tafsir literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exegesisField Context triple: [Qur’an 46:13, exegesisField, tafsir literature]
-
A.
hasExegesisBy
Indicates that an entity (such as a text or passage) is the subject of an exegesis authored or provided by another entity.
-
B.
styleOfExegesis
Indicates the particular interpretive method or approach applied when analyzing or explaining a text.
-
C.
scripturalCorpusAnalyzed
chosen
Indicates that a particular scriptural corpus has been examined or studied, typically in a systematic or scholarly manner.
-
D.
scripturalExpertise
Indicates a relationship where one entity possesses specialized knowledge or authoritative understanding of religious scriptures in relation to another entity or context.
-
E.
evaluationInBible
Indicates an assessment, judgment, or characterization of something as it appears or is treated within the context of the Bible.
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:06 p.m.