Triple
T25814630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahl al-Bayt |
E650214
|
entity |
| Predicate | associatedHadith |
P33139
|
FINISHED |
| Object | Hadith al-Kisa |
—
|
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: Hadith al-Kisa | Statement: [Ahl al-Bayt, associatedHadith, Hadith al-Kisa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedHadith Context triple: [Ahl al-Bayt, associatedHadith, Hadith al-Kisa]
-
A.
describedInHadithAs
Indicates that something is mentioned, characterized, or narrated within a hadith text.
-
B.
hadithCollections
Indicates a relationship where one entity is a collection that contains, organizes, or compiles hadiths (reports of the sayings, actions, or approvals of the Prophet).
-
C.
hadithsNarrated
Indicates that one entity (typically a person) has narrated, transmitted, or reported the hadiths associated with another entity (such as a collection, text, or individual hadith).
-
D.
basedOnHadith
chosen
Indicates that something is derived from, supported by, or directly referencing a specific hadith.
-
E.
sourceOfHadithFor
Indicates that one entity serves as the originating source or transmitter for a particular hadith associated with another entity.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
Created at: April 22, 2026, 7:25 a.m.