Triple
T1324356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramadan |
E28290
|
entity |
| Predicate | fastingTimeframe |
P302
|
FINISHED |
| Object | from true dawn (fajr) to sunset (maghrib) |
—
|
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: from true dawn (fajr) to sunset (maghrib) | Statement: [Ramadan, fastingTimeframe, from true dawn (fajr) to sunset (maghrib)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fastingTimeframe Context triple: [Ramadan, fastingTimeframe, from true dawn (fajr) to sunset (maghrib)]
-
A.
fastingRuleVariation
Indicates a modification or alternative form of a standard fasting rule or practice.
-
B.
preparatoryFastBegins
Indicates that a required period of fasting starts in preparation for a subsequent event, action, or ritual.
-
C.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
D.
focusPeriod
Indicates the specific time span during which attention, activity, or analysis is concentrated on something.
-
E.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c19e81c0819092f85201ae34422a |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beedb49c8190beb5b85cdda05013 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.