Triple
T26138487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tahmid |
E659447
|
entity |
| Predicate | oftenRecitedIn |
P33123
|
FINISHED |
| Object | sermons (khutbahs) |
—
|
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: sermons (khutbahs) | Statement: [Tahmid, oftenRecitedIn, sermons (khutbahs)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenRecitedIn Context triple: [Tahmid, oftenRecitedIn, sermons (khutbahs)]
-
A.
isOftenRecitedFor
Indicates that something (such as a text, phrase, or piece of music) is frequently spoken, chanted, or performed for a particular purpose, audience, or occasion.
-
B.
recitedOnOccasion
chosen
Indicates that something (typically a text, speech, or performance) was recited during or in connection with a specific occasion or event.
-
C.
recites
Indicates that one entity verbally delivers or repeats from memory the words, text, or performance associated with another entity.
-
D.
mayBeRecited
Indicates that something is permitted or suitable to be spoken aloud or recited, typically in a formal or ritualized manner.
-
E.
oftenCitedAs
Indicates that one entity is frequently referenced or mentioned as an example, source, or authority in relation to 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 26, 2026, 8:18 p.m.