Triple
T15679270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hadith of the Cloak |
E377527
|
entity |
| Predicate | linkedVerse |
P114904
|
FINISHED |
| Object | Quran 33:33 |
—
|
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: Quran 33:33 | Statement: [Hadith of the Cloak, linkedVerse, Quran 33:33]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedVerse Context triple: [Hadith of the Cloak, linkedVerse, Quran 33:33]
-
A.
keyVerse
Indicates that one verse is designated as the central or most thematically important verse in relation to a text, passage, or concept.
-
B.
associatedWithVerse
chosen
Indicates a relationship where something is linked or connected to a specific verse, typically in a text or scripture.
-
C.
verses
Indicates a relationship where one entity competes or is pitted against another, as in an opposition, matchup, or comparison.
-
D.
containsVerse
Indicates that one entity (typically a text or collection) includes a specific verse as part of its content.
-
E.
associatedWithPoem
Indicates a relationship in which an entity is connected or linked to a particular poem, such as by authorship, subject, reference, or contextual association.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f2f1640819086efd5a73bb9734a |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:16 a.m.