Triple
T511223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purim |
E10611
|
entity |
| Predicate | religiousDuty |
P2154
|
FINISHED |
| Object | hearing the Megillah |
—
|
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: hearing the Megillah | Statement: [Purim, religiousDuty, hearing the Megillah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousDuty Context triple: [Purim, religiousDuty, hearing the Megillah]
-
A.
religiousFunction
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
-
B.
religiousElement
chosen
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
C.
religiousConsequence
Indicates a relationship where one event, action, or state leads to an outcome specifically defined or understood in religious terms (such as divine reward, punishment, obligation, or spiritual effect).
-
D.
religiousTarget
Indicates that an action, policy, or behavior is directed at someone or something specifically because of their religion or religious affiliation.
-
E.
religiousClaim
Indicates that an entity asserts, expresses, or is associated with a statement or belief grounded in religion or spiritual doctrine.
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f165b91c81908c2d2ba15c64b956 |
completed | Feb. 28, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69a2edfe236481909901cc7d4281b33c |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.