Triple
T8989743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Id al-Adha |
E214757
|
entity |
| Predicate | prayerTime |
P33138
|
FINISHED |
| Object | after sunrise and before midday on the 10th of Dhu al-Hijjah |
—
|
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: after sunrise and before midday on the 10th of Dhu al-Hijjah | Statement: [Id al-Adha, prayerTime, after sunrise and before midday on the 10th of Dhu al-Hijjah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prayerTime Context triple: [Id al-Adha, prayerTime, after sunrise and before midday on the 10th of Dhu al-Hijjah]
-
A.
prayerTiming
chosen
Indicates the scheduled or appropriate time at which a prayer or act of worship is to be performed.
-
B.
positionInFiveDailyPrayers
Indicates the specific ordinal place that a given prayer occupies within the sequence of the five daily prayers.
-
C.
adhanRequired
Indicates that the Islamic call to prayer (adhan) must be performed or is obligatory in the given context or situation.
-
D.
prayerCall
Indicates that one entity issues or performs a call to prayer directed toward others.
-
E.
praysAt
Indicates that one entity performs an act of prayer at, or directed toward, a specific place or site.
- 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_69ca839f76bc8190a4b7123cdd682199 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc687205c88190a4cdf12ee2cdfd14 |
completed | April 1, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69cc5edba0f88190b97401636a076d7a |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:04 p.m.