Triple
T30818482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Six Books |
E784851
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | canonical hadith collections |
C27895
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: canonical hadith collections Context triple: [Six Books, instanceOf, canonical hadith collections]
-
A.
hadith collection section
A hadith collection section is an organized subdivision within a hadith compilation that groups individual prophetic narrations by topic, book, or chapter for systematic study and reference.
-
B.
supplementary hadith compilation
A supplementary hadith compilation is a curated collection of prophetic traditions assembled to complement primary hadith corpora by adding additional narrations, variants, or chains of transmission for further clarification and study.
-
C.
hadith book
A hadith book is a compiled collection of narrations reporting the sayings, actions, approvals, and characteristics of the Prophet Muhammad, organized for religious guidance and scholarly reference.
-
D.
hadith commentary collection
A hadith commentary collection is an organized compilation of explanatory works that analyze, interpret, and contextualize prophetic traditions to clarify their meanings, implications, and applications.
-
E.
hadith collection genre
chosen
The hadith collection genre comprises curated compilations of prophetic reports, systematically gathered, authenticated, and organized to preserve and transmit the sayings, actions, and approvals of the Prophet Muhammad for religious, legal, and ethical guidance.
- F. None of above.
Provenance (1 batch)
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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:44 p.m.