Triple
T6718460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muharram |
E153332
|
entity |
| Predicate | traditionalPracticeInSunniIslam |
P59382
|
FINISHED |
| Object | fasting on Ashura |
—
|
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: fasting on Ashura | Statement: [Muharram, traditionalPracticeInSunniIslam, fasting on Ashura]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalPracticeInSunniIslam Context triple: [Muharram, traditionalPracticeInSunniIslam, fasting on Ashura]
-
A.
statusInIslamicTradition
Indicates the recognized standing, role, or level of esteem an entity holds within Islamic religious, cultural, or scholarly tradition.
-
B.
viewInSunniTheology
Indicates the perspective or doctrinal position held within Sunni Islamic theology regarding a given concept, figure, or issue.
-
C.
uniformTradition
Indicates that multiple entities follow the same established customs, practices, or conventions in a consistent manner.
-
D.
practicedTradition
chosen
Indicates that an entity engages in or carries out a particular tradition as a customary or repeated practice.
-
E.
positionInIslam
Indicates the specific religious role, rank, or status an entity holds within the context of Islam.
- 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_69c68809b4608190a2509ddb5ab87f05 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d135d27c819088c45839ad0e7bab |
completed | March 27, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69c6d08c5d348190a29dee668c398e70 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:07 p.m.