Triple
T36099764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hussainiyah |
E1044168
|
entity |
| Predicate | notableOccasion |
P89869
|
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: [Hussainiyah, notableOccasion, Muharram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableOccasion Context triple: [Hussainiyah, notableOccasion, Muharram]
-
A.
notableCelebration
Indicates that an entity is especially recognized or distinguished for celebrating, commemorating, or observing a particular event, occasion, or practice.
-
B.
specialOccasion
Indicates that an event or situation is associated with a notable or exceptional occasion, such as a celebration, milestone, or culturally significant date.
-
C.
marksOccasion
Indicates that an event, action, or item serves to commemorate, celebrate, or formally recognize a particular occasion or milestone.
-
D.
occasionType
chosen
Indicates the specific kind or category of occasion or event associated with the subject.
-
E.
primaryOccasion
Indicates that one occasion is the main or most significant event associated with a given context, entity, or activity.
- 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_69f76e338e2c8190b7f3bc68bec76349 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38d54c827081909ec1924509525351 |
completed | June 22, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.