Triple
T32293257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Asian Shia Muslims |
E825021
|
entity |
| Predicate | notableRitualMonth |
P108106
|
FINISHED |
| Object | Muharram |
E153332
|
NE 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: Muharram | Statement: [South Asian Shia Muslims, notableRitualMonth, Muharram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRitualMonth Context triple: [South Asian Shia Muslims, notableRitualMonth, Muharram]
-
A.
consideredSacredMonth
Indicates that a particular month is regarded or designated as sacred within a given religious, cultural, or traditional context.
-
B.
liturgicalMonth
chosen
Indicates that something is associated with, occurs in, or pertains to a specific month within a liturgical or religious calendar.
-
C.
sacredMonthGroup
Indicates that the related entities belong to the same designated group of sacred or holy months.
-
D.
sacredMonthNumber
Indicates the numerical position or identifier assigned to a month that is considered sacred within a particular calendar or religious system.
-
E.
majorFestivalMonthGregorian
Indicates the Gregorian calendar month in which a major festival associated with an entity takes place.
- F. None of above.
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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f46f255508190bbd0afce722ffb6e |
completed | June 15, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:44 a.m.