Triple
T457641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yom HaShoah |
E7267
|
entity |
| Predicate | typeOfDay |
P3004
|
FINISHED |
| Object | day of remembrance |
—
|
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: day of remembrance | Statement: [Yom HaShoah, typeOfDay, day of remembrance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDay Context triple: [Yom HaShoah, typeOfDay, day of remembrance]
-
A.
typeOfDate
Indicates that one entity specifies the category or kind of date (e.g., start date, end date, due date) that characterizes another date-related entity or value.
-
B.
schoolDayType
chosen
Indicates the classification of a given day according to its role in the school calendar (e.g., regular school day, holiday, exam day, etc.).
-
C.
DSTType
Indicates the type or classification of daylight saving time (DST) applied to a given time zone or region.
-
D.
termType
Indicates the classification or category of a term within a system, specifying what kind of term it is (e.g., type, role, or function) in relation to others.
-
E.
observesDay
Indicates that an entity recognizes, commemorates, or practices a particular day (such as a holiday, event, or observance) according to some calendar or tradition.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efa3163081909acff040a22bd559 |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede614b88190be07425f5535f56d |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.