Triple
T3072399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mordechai |
E64053
|
entity |
| Predicate | holidayPractice |
P5814
|
FINISHED |
| Object | name is recited during Purim services |
—
|
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: name is recited during Purim services | Statement: [Mordechai, holidayPractice, name is recited during Purim services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holidayPractice Context triple: [Mordechai, holidayPractice, name is recited during Purim services]
-
A.
holidayType
Indicates the specific category or kind of holiday associated with an event or date (e.g., public, religious, national, or personal).
-
B.
holidayRole
Indicates the specific function, duty, or part an entity plays in relation to a holiday or holiday-related event.
-
C.
holidaySchedule
Indicates the planned dates, times, and durations during which holidays occur or are observed.
-
D.
traditionalHoliday
Indicates that an event or celebration is recognized as a customary or long-established holiday within a culture or community.
-
E.
holidayAssociation
chosen
Indicates a relationship where one entity is connected to, themed around, or designated for a particular holiday.
- 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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada14c8bd881909cf1bb2649ba36db |
completed | March 8, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69ad9625b30c819099ef9349c91d7b25 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.