Triple
T25827804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Father of Flame |
E650580
|
entity |
| Predicate | quranicSurahAlternativeName |
P75743
|
FINISHED |
| Object | al-Lahab |
—
|
NE NERFINISHED |
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: al-Lahab | Statement: [Father of Flame, quranicSurahAlternativeName, al-Lahab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: quranicSurahAlternativeName Context triple: [Father of Flame, quranicSurahAlternativeName, al-Lahab]
-
A.
quranSurahAlternateName
chosen
Indicates that a particular name is an alternate or secondary title used to refer to a specific surah of the Quran.
-
B.
quranicSurah
Indicates that one entity is a chapter (surah) of the Quran associated with or identified by the other entity.
-
C.
quranSurahNumber
Indicates the numerical position or identifier assigned to a specific surah (chapter) within the Quran.
-
D.
rukūʿNumberInSurah
Indicates the number or position of a specific rukūʿ (section of verses) within a given surah.
-
E.
quranicSurahMention
Indicates that a specific Quranic surah is mentioned, referenced, or cited in relation to another entity or context.
- 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_69e7ab37438081908f1ccf6284839520 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60196db508190956c0b7cbc66d4df |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 22, 2026, 7:37 a.m.