Triple
T2254978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surah Al-Qamar |
E49700
|
entity |
| Predicate | firstVerseText |
P36750
|
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 Al-Qamar, firstVerseText, اقْتَرَبَتِ السَّاعَةُ وَانشَقَّ الْقَمَرُ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstVerseText Context triple: [Surah Al-Qamar, firstVerseText, اقْتَرَبَتِ السَّاعَةُ وَانشَقَّ الْقَمَرُ]
-
A.
refrainText
Indicates that a piece of text functions as the recurring refrain or repeated line within a larger work, such as a song or poem.
-
B.
firstWord
Indicates that one entity is the first word in the sequence or text associated with another entity.
-
C.
firstLineTranslation
Indicates that one text is a translation of the first line of another text.
-
D.
keyVerse
Indicates that one verse is designated as the central or most thematically important verse in relation to a text, passage, or concept.
-
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_69a88aaa9250819095e127d0d77e8a32 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc121af78819085b2e601d2f9bcdf |
completed | March 7, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69abbdb34c148190b51e99f540f97204 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe86dbcc81908c72793af8fe2a4d |
completed | March 7, 2026, 5:58 a.m. |
Created at: March 4, 2026, 7:47 p.m.