Triple
T4938611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aisne-Marne American Cemetery |
E110872
|
entity |
| Predicate | hasCommemorativeEvents |
P27243
|
FINISHED |
| Object | Memorial Day ceremonies |
—
|
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: Memorial Day ceremonies | Statement: [Aisne-Marne American Cemetery, hasCommemorativeEvents, Memorial Day ceremonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommemorativeEvents Context triple: [Aisne-Marne American Cemetery, hasCommemorativeEvents, Memorial Day ceremonies]
-
A.
commemorativeEvent
chosen
Indicates an event held specifically to honor, remember, or mark the significance of a person, group, or past occurrence.
-
B.
commemoratesEventWith
Indicates that one entity serves as a memorial or tribute to a specific event, marking or honoring its occurrence.
-
C.
commemoratesEventOn
Indicates that one entity marks, honors, or observes a specific event on a particular date or occasion.
-
D.
hasCommemorationFunction
Indicates that something serves the role or purpose of commemorating an event, person, group, or concept.
-
E.
periodCommemorated
Indicates that something serves to honor, remember, or mark a specific historical or temporal period.
- 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_69bd4415eee08190bdce70276e56a5b4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd7088f6e48190bf09e58ab053a4d1 |
completed | March 20, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69bd6c389b9881908ad7fb1c5393c1b1 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:31 p.m.