Triple
T15679295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muhammad ibn Ya‘qub al-Kulayni |
E377528
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hadith compiler |
C35710
|
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: hadith compiler Context triple: [Muhammad ibn Ya‘qub al-Kulayni, instanceOf, hadith compiler]
-
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.
hadith transmitter
A hadith transmitter is an individual who narrates and conveys reports of the sayings, actions, or approvals of the Prophet Muhammad through an authenticated chain of transmission.
-
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.
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.
-
E.
hadith collection genre
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. chosen
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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:16 a.m.