Triple
T13660166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remembrance of the Dead |
E326973
|
entity |
| Predicate | startPeriodOfCommemoration |
P66044
|
FINISHED |
| Object | since the outbreak of World War II |
—
|
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: since the outbreak of World War II | Statement: [Remembrance of the Dead, startPeriodOfCommemoration, since the outbreak of World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startPeriodOfCommemoration Context triple: [Remembrance of the Dead, startPeriodOfCommemoration, since the outbreak of World War II]
-
A.
commemorationStart
Indicates the point in time when a commemorative event or observance begins.
-
B.
commemoratedSince
chosen
Indicates that a commemoration of one entity for another has been in effect starting from a specific point in time.
-
C.
commemoratedYear
Indicates the specific year in which an event, person, or entity is formally remembered, honored, or celebrated.
-
D.
periodCommemorated
Indicates that something serves to honor, remember, or mark a specific historical or temporal period.
-
E.
commemoratedOn
Indicates that something is remembered, honored, or celebrated on a specific date or occasion.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc61f0d808190b1cd2a6ba0d930eb |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:52 p.m.