Triple
T4077744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memorial Day |
E87404
|
entity |
| Predicate | observanceChangeYear |
P20588
|
FINISHED |
| Object | 1971 |
—
|
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: 1971 | Statement: [Memorial Day, observanceChangeYear, 1971]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observanceChangeYear Context triple: [Memorial Day, observanceChangeYear, 1971]
-
A.
observanceMayVaryByYear
chosen
Indicates that the way an observance is recognized, scheduled, or practiced can differ from one year to another.
-
B.
observesAllYear
Indicates that the observing entity continuously observes or monitors the target entity throughout the entire year without interruption.
-
C.
newYearOccursIn
Indicates that the celebration or observance of New Year takes place within a specified temporal or calendrical context (such as a particular month, season, or year).
-
D.
observance
Indicates the performance or maintenance of a practice, rule, or custom in accordance with prescribed or expected standards.
-
E.
observanceRequires
Indicates that carrying out a particular observance or practice is contingent upon, or must be accompanied by, the fulfillment of a specified requirement or condition.
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc4d348c8190a94724639830aca0 |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9082c2081908474f082a49bebc8 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.