Triple
T24377520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kitab al-Athar |
E614517
|
entity |
| Predicate | typeOfHadithWork |
P155972
|
FINISHED |
| Object | musannaf-style collection |
—
|
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: musannaf-style collection | Statement: [Kitab al-Athar, typeOfHadithWork, musannaf-style collection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfHadithWork Context triple: [Kitab al-Athar, typeOfHadithWork, musannaf-style collection]
-
A.
sourceOfHadithFor
Indicates that one entity serves as the originating source or transmitter for a particular hadith associated with another entity.
-
B.
roleInHadith
Indicates the specific function, position, or participation an entity has within the context or transmission of a hadith.
-
C.
statusInHadith
Indicates the classification or standing of a hadith (such as authentic, weak, or fabricated) within hadith scholarship.
-
D.
statusInHadithScience
Indicates the evaluative standing or classification an entity holds within the methodological framework of hadith scholarship and criticism.
-
E.
hadithCategory
Indicates that a hadith is classified under a particular category or type within hadith literature.
- F. None of above. chosen
Provenance (4 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293d96e7c8190b2f33a8fd12c32c6 |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:02 a.m.