Triple
T5808601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suresnes American Cemetery |
E128809
|
entity |
| Predicate | hasMemorialTabletsFor |
P66448
|
FINISHED |
| Object | missing in action 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: missing in action of World War II | Statement: [Suresnes American Cemetery, hasMemorialTabletsFor, missing in action of World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemorialTabletsFor Context triple: [Suresnes American Cemetery, hasMemorialTabletsFor, missing in action of World War II]
-
A.
hasMemorial
Indicates that a memorial exists in honor of, or dedicated to, a particular entity.
-
B.
hasGraveInscription
Indicates that an entity (typically a grave or tomb) bears a specific inscription engraved or written on it.
-
C.
hasPartInMausoleum
Indicates that an entity is a component, section, or element contained within or forming part of a mausoleum.
-
D.
hasMausoleum
Indicates that one entity possesses, contains, or is associated with a mausoleum dedicated to another entity.
-
E.
hasAdjacentMemorial
Indicates that one memorial is located directly next to or in close proximity to another memorial.
- F. None of above. chosen
Provenance (4 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_69c0084788848190bcf71f6bc5d71597 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b1867a481909a7ea3331dbb04ce |
completed | March 22, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69c021d5ecd081908a62dd66e26f8598 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c028ffe180819099e084fe557e789c |
completed | March 22, 2026, 5:38 p.m. |
Created at: March 22, 2026, 3:52 p.m.