Triple
T2570465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yom HaZikaron |
E57652
|
entity |
| Predicate | timeOfDayEnds |
P35259
|
FINISHED |
| Object | following sunset at the start of Yom HaAtzmaut |
—
|
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: following sunset at the start of Yom HaAtzmaut | Statement: [Yom HaZikaron, timeOfDayEnds, following sunset at the start of Yom HaAtzmaut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfDayEnds Context triple: [Yom HaZikaron, timeOfDayEnds, following sunset at the start of Yom HaAtzmaut]
-
A.
typicalEndHourLocal
Indicates the usual local-time clock hour at which an activity, event, or operation typically ends.
-
B.
timeZoneAtUSEnd
Indicates the time zone that applies at the end point of a U.S.-based event, interval, or usage period.
-
C.
DSTEndRule
Indicates the rule or condition that specifies when daylight saving time ends in a given timekeeping system.
-
D.
nightService
Indicates that a service operates or is available during nighttime hours.
-
E.
timePeriodEndApprox
chosen
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
- 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_69ab4a51410081908501dcf8bad9adc4 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd382928c8190b6316f3db48d8e73 |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0ce4dcc8190b17a65abf9bd1bb0 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.