Triple
T1917747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Festival of Sacrifice |
E40055
|
entity |
| Predicate | prayerTiming |
P33138
|
FINISHED |
| Object | morning |
—
|
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: morning | Statement: [Festival of Sacrifice, prayerTiming, morning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prayerTiming Context triple: [Festival of Sacrifice, prayerTiming, morning]
-
A.
numberOfRakats
Indicates the specific count of prayer units (rakats) associated with a given prayer or ritual act.
-
B.
prayerCall
Indicates that one entity issues or performs a call to prayer directed toward others.
-
C.
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.
-
D.
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.
-
E.
positionInIslamicCalendar
Indicates the specific placement or ordering of a time point (such as a date or event) within the structure of the Islamic (Hijri) calendar.
- F. None of above. chosen
Provenance (4 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb2107fe48190bafff825f1f805ad |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafed2ab481908920334e77b1021b |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb1b180e481908bbe893d6ba6208b |
completed | March 7, 2026, 5:03 a.m. |
Created at: March 4, 2026, 7:35 p.m.