Triple
T13135691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arbaeen (40th day after Ashura) |
E312075
|
entity |
| Predicate | daysAfterAshura |
P108368
|
FINISHED |
| Object | 40 |
—
|
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: 40 | Statement: [Arbaeen (40th day after Ashura), daysAfterAshura, 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: daysAfterAshura Context triple: [Arbaeen (40th day after Ashura), daysAfterAshura, 40]
-
A.
dayInBadíCalendar
Indicates that a given day corresponds to a specific day position within the Badí (Bahá’í) calendar system.
-
B.
timeframeRelativeToRoshHashanah
Indicates the temporal relationship of an event or period in reference to Rosh Hashanah (e.g., before, during, or after the holiday).
-
C.
dayRelativeToEaster
Indicates the temporal offset of a given day relative to the date of Easter in a specific year (e.g., days before or after Easter Sunday).
-
D.
conversionToMosqueDate
Indicates the date on which a building or site was converted into a mosque.
-
E.
religiousCalendar
Indicates that there is an association between an entity and a system of dates and observances defined by a particular religion or religious tradition.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981b53fbc8190a0f209c32a00f6cb |
completed | April 10, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69d9804543cc8190a23cd7da59a12a7b |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d980e622e8819087a69bfb1660dd64 |
completed | April 10, 2026, 10:59 p.m. |
Created at: April 9, 2026, 9:08 p.m.