Triple
T34994602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quran 83:1 |
E1009488
|
entity |
| Predicate | setsToneForSurah |
P182187
|
FINISHED |
| Object | condemnation of cheating and injustice |
—
|
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: condemnation of cheating and injustice | Statement: [Quran 83:1, setsToneForSurah, condemnation of cheating and injustice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsToneForSurah Context triple: [Quran 83:1, setsToneForSurah, condemnation of cheating and injustice]
-
A.
commandInSurah
Indicates that a particular command or directive appears within a specified surah (chapter) of the Quran.
-
B.
ordersSurahsPrimarilyBy
Indicates that one entity arranges or sequences surahs chiefly according to a specified organizing principle or criterion.
-
C.
themeInQuran
Indicates that a particular theme, concept, or topic is present in and addressed by the Quran.
-
D.
quranicSurah
Indicates that one entity is a chapter (surah) of the Quran associated with or identified by the other entity.
-
E.
includeSurah
Indicates that one entity (such as a collection, book, or document) contains or incorporates a specific Surah as part of its contents.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7870dfe108190996c0c68630edc7f |
completed | May 3, 2026, 5:34 p.m. |
Created at: May 3, 2026, 4:01 p.m.