Triple
T26947305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jish |
E678680
|
entity |
| Predicate | religiousHolidayObserved |
P111126
|
FINISHED |
| Object | Christian holidays |
—
|
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: Christian holidays | Statement: [Jish, religiousHolidayObserved, Christian holidays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousHolidayObserved Context triple: [Jish, religiousHolidayObserved, Christian holidays]
-
A.
religiousHolidayCelebrated
chosen
Indicates that a particular religious holiday is observed or celebrated by an entity.
-
B.
religiousHolidayContext
Indicates that an event, action, or situation occurs within the setting, timeframe, or circumstances of a religious holiday or observance.
-
C.
ethnicHoliday
Indicates a holiday that is specifically associated with, celebrated by, or originating from a particular ethnic group.
-
D.
religiousCalendar
Indicates that there is an association between an entity and a system of dates and observances defined by a particular religion or religious tradition.
-
E.
relatedHoliday
Indicates that there is an association or connection between two holidays, such as thematic, temporal, cultural, or contextual relatedness.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 27, 2026, 6:22 a.m.