Triple
T3393639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surah At-Takathur |
E71475
|
entity |
| Predicate | verse4Arabic |
P17618
|
FINISHED |
| Object | ثُمَّ كَلَّا سَوْفَ تَعْلَمُونَ |
—
|
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: ثُمَّ كَلَّا سَوْفَ تَعْلَمُونَ | Statement: [Surah At-Takathur, verse4Arabic, ثُمَّ كَلَّا سَوْفَ تَعْلَمُونَ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verse4Arabic Context triple: [Surah At-Takathur, verse4Arabic, ثُمَّ كَلَّا سَوْفَ تَعْلَمُونَ]
-
A.
quranicVerse
chosen
Indicates that a given text segment is a verse from the Quran and encodes the relationship between that verse and its source scripture.
-
B.
sajdahVerseNumber
Indicates the verse number in a chapter at which a prostration (sajdah) is prescribed or occurs.
-
C.
quranicSurah
Indicates that one entity is a chapter (surah) of the Quran associated with or identified by the other entity.
-
D.
quranSection
Indicates that one entity is a section, passage, or subdivided part of the Quran associated with another entity.
-
E.
verses
Indicates a relationship where one entity competes or is pitted against another, as in an opposition, matchup, or comparison.
- 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb853746c8190bfa1447e6ebbefb3 |
completed | March 8, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.