Triple
T21706956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taraweeh prayers |
E535794
|
entity |
| Predicate | hasRakaatNumber |
P28128
|
FINISHED |
| Object | 8 rakaat (common view) |
—
|
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: 8 rakaat (common view) | Statement: [Taraweeh prayers, hasRakaatNumber, 8 rakaat (common view)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRakaatNumber Context triple: [Taraweeh prayers, hasRakaatNumber, 8 rakaat (common view)]
-
A.
numberOfRakats
chosen
Indicates the specific count of prayer units (rakats) associated with a given prayer or ritual act.
-
B.
optionalRakatsType
Indicates that a particular type or number of rakats (units of Islamic prayer) is optionally associated with or applicable to an action, event, or prayer.
-
C.
includesOptionalRakats
Indicates that the relationship or action involves the inclusion of optional rakats (units of prayer) as part of a broader prayer or ritual sequence.
-
D.
hasPrayerRite
Indicates that one entity is associated with, follows, or practices a particular prayer rite or liturgical form.
-
E.
sajdahVerseNumber
Indicates the verse number in a chapter at which a prostration (sajdah) is prescribed or occurs.
- 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.