Triple
T696600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tishrei |
E13906
|
entity |
| Predicate | day1Event |
P17593
|
FINISHED |
| Object | Rosh Hashanah first day |
—
|
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: Rosh Hashanah first day | Statement: [Tishrei, day1Event, Rosh Hashanah first day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: day1Event Context triple: [Tishrei, day1Event, Rosh Hashanah first day]
-
A.
event
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
-
B.
annualEvent
Indicates that an event occurs once every year on a recurring basis.
-
C.
eventDescription
Indicates that a textual summary or explanation is provided describing what happens in the event.
-
D.
eveCelebrationOn
Indicates that an event or entity is engaged in or associated with a celebration occurring on a specific date or occasion.
-
E.
typicalEvent
Indicates that the associated event is a common, characteristic, or prototypical occurrence for the given entity or situation.
- F. None of above. chosen
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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0c8055881909565ebde2be8fd7a |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d23e0a08190b08be9d1eff2a1bb |
completed | March 1, 2026, 8:10 p.m. |
| PDg | Predicate description generation | batch_69a49df19c9481909cc9bc33ed7f011b |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:36 p.m.