Triple
T21706953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taraweeh prayers |
E535794
|
entity |
| Predicate | oftenLeadsToCompletionOf |
P18658
|
FINISHED |
| Object | entire Qur’an |
—
|
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: entire Qur’an | Statement: [Taraweeh prayers, oftenLeadsToCompletionOf, entire Qur’an]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenLeadsToCompletionOf Context triple: [Taraweeh prayers, oftenLeadsToCompletionOf, entire Qur’an]
-
A.
completionOf
Indicates that one entity represents the finished state, fulfillment, or successful conclusion of another entity, process, or requirement.
-
B.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
C.
completionRelatedTo
Indicates that one entity’s completion, fulfillment, or finishing is connected to, dependent on, or relevant for another entity.
-
D.
supportsCompletion
Indicates that one entity enables, facilitates, or is compatible with the successful completion of another entity’s process, task, or operation.
-
E.
canLeadTo
chosen
Indicates that one entity, condition, or event has the potential to cause, result in, or bring about another.
- 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efb530779c819080204c3bd2f6afa2 |
completed | April 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:46 p.m.