Triple
T34455440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Pleading Woman |
E884490
|
entity |
| Predicate | isPrecededBySurah |
P30312
|
FINISHED |
| Object | Surah Al-Hadid |
—
|
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: Surah Al-Hadid | Statement: [The Pleading Woman, isPrecededBySurah, Surah Al-Hadid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrecededBySurah Context triple: [The Pleading Woman, isPrecededBySurah, Surah Al-Hadid]
-
A.
precedesSurah
Indicates that one surah comes immediately before another surah in the ordered sequence of surahs.
-
B.
hasSunnahBefore
Indicates that there is an established Sunnah (prophetic practice) prayer or action that is to be performed before a given main act of worship or event.
-
C.
followsSurah
chosen
Indicates that one surah directly comes after or is ordered immediately following another surah in a specified sequence.
-
D.
omittedAtStartOfSurah
Indicates that something (such as a phrase, verse, or formula) is left out or not present at the beginning of a surah.
-
E.
hasCanonicalOrderInQuran
Indicates that there is a specific, officially recognized sequence or position of something within the canonical ordering of 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71976c49c8190943046a0ff8950cb |
completed | May 3, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2 a.m.