Triple
T3133367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surah Al-Fajr |
E65468
|
entity |
| Predicate | finalVersesPromise |
P45564
|
FINISHED |
| Object | entry into Paradise |
—
|
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: entry into Paradise | Statement: [Surah Al-Fajr, finalVersesPromise, entry into Paradise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalVersesPromise Context triple: [Surah Al-Fajr, finalVersesPromise, entry into Paradise]
-
A.
closingVerse
Indicates that one entity serves as the final or concluding verse of another entity, such as a song, poem, or hymn.
-
B.
finalValue
Indicates the resulting or ultimate value obtained after all relevant operations, changes, or calculations have been completed.
-
C.
verses
Indicates a relationship where one entity competes or is pitted against another, as in an opposition, matchup, or comparison.
-
D.
finalPhaseOf
Indicates that one process, stage, or event constitutes the concluding or last phase of another broader process or sequence.
-
E.
containsVerse
Indicates that one entity (typically a text or collection) includes a specific verse as part of its content.
- F. None of above. chosen
Provenance (4 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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada56104ec8190a14591ed73f3fe83 |
completed | March 8, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69ad9df840088190a26a1516f4c1f056 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f7c21c819087e9992f5fe30a37 |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:04 p.m.