Triple
T8653825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paradise (Islam) |
E205161
|
entity |
| Predicate | scripturalPromiseType |
P2326
|
FINISHED |
| Object | divine promise |
—
|
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: divine promise | Statement: [Paradise (Islam), scripturalPromiseType, divine promise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scripturalPromiseType Context triple: [Paradise (Islam), scripturalPromiseType, divine promise]
-
A.
promiseOfBlessingTo
Indicates that one entity has declared or assured a future blessing or favorable outcome to another entity.
-
B.
scriptureType
Indicates the classification or category of a scripture in relation to its type or genre.
-
C.
typeOfProphecy
Indicates the specific category or kind of prophecy that a given prophetic statement or vision belongs to.
-
D.
scripturalBasis
chosen
Indicates that one entity serves as the religious or scriptural foundation, support, or justification for another entity (such as a belief, practice, or doctrine).
-
E.
receivedScripture
Indicates that one entity has been given or accepted a body of sacred or authoritative religious writings from another source.
- 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_69ca834e56848190abb0eeaec9dedd32 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc48432568819093b9a867b4f62b78 |
completed | March 31, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:29 p.m.