Triple
T24294890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asr |
E605929
|
entity |
| Predicate | hasSunnahAfter |
P47020
|
FINISHED |
| Object | no emphasized sunnah after (majority view) |
—
|
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: no emphasized sunnah after (majority view) | Statement: [Asr, hasSunnahAfter, no emphasized sunnah after (majority view)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSunnahAfter Context triple: [Asr, hasSunnahAfter, no emphasized sunnah after (majority view)]
-
A.
hasLastSutra
Indicates that one entity is the final or concluding sutra associated with another entity.
-
B.
hasSubsequent
chosen
Indicates that one entity occurs, appears, or is positioned after another in a defined sequence or order.
-
C.
hasHadithMerit
Indicates that there exists supporting or relevant hadith evidence conferring merit, validation, or special status upon the associated entity or action.
-
D.
hasSahn
Indicates that an entity possesses or includes a sahn (a courtyard, typically in traditional Islamic or Middle Eastern architecture).
-
E.
hasHadithReference
Indicates that there exists a reference or citation linking something to a specific hadith source or passage.
- 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f291593c0881908a6827f0d8899fe6 |
completed | April 29, 2026, 11:16 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 12:09 a.m.