Triple
T3965912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Normandy American Cemetery and Memorial |
E92215
|
entity |
| Predicate | hasAnnualCeremony |
P9704
|
FINISHED |
| Object | D-Day anniversary commemoration |
—
|
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: D-Day anniversary commemoration | Statement: [Normandy American Cemetery and Memorial, hasAnnualCeremony, D-Day anniversary commemoration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnnualCeremony Context triple: [Normandy American Cemetery and Memorial, hasAnnualCeremony, D-Day anniversary commemoration]
-
A.
ceremonyYear
Indicates the year in which a particular ceremony took place.
-
B.
goldAwardCeremonyTypicallyHeldAt
Indicates the usual location or venue where a gold award ceremony is held.
-
C.
awardCeremonyOccasion
Indicates that an award ceremony is held on, or in connection with, a particular occasion or event.
-
D.
annualPerformances
chosen
Indicates that performances or events occur on a yearly or once-per-year basis.
-
E.
ceremonyHeld
Indicates that a formal ceremony or ritual event has taken place at a particular time and/or location.
- 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_69aed96624188190ac8c45bb57ab72b5 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefba878a48190a2e234d775215938 |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef8efcf3c81908ccf61d9ce26b0c0 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:32 p.m.