Triple
T14313424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | At-Takathur |
E354891
|
entity |
| Predicate | surahOrderInMushaf |
P26928
|
FINISHED |
| Object | 102 |
—
|
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: 102 | Statement: [At-Takathur, surahOrderInMushaf, 102]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surahOrderInMushaf Context triple: [At-Takathur, surahOrderInMushaf, 102]
-
A.
chronologicalOrderOfFullSurah
Indicates the sequential position of a complete surah within an ordered timeline or arrangement.
-
B.
quranicSurah
Indicates that one entity is a chapter (surah) of the Quran associated with or identified by the other entity.
-
C.
includeSurah
Indicates that one entity (such as a collection, book, or document) contains or incorporates a specific Surah as part of its contents.
-
D.
commandInSurah
Indicates that a particular command or directive appears within a specified surah (chapter) of the Quran.
-
E.
quranSurahNumber
chosen
Indicates the numerical position or identifier assigned to a specific surah (chapter) within the Quran.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85b49e5481909b9ffab2d922e284 |
completed | April 14, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:12 a.m.