Triple
T17135449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Last Post ceremony at the Menin Gate |
E415823
|
entity |
| Predicate | resumedOn |
P44197
|
FINISHED |
| Object | 6 May 1945 |
—
|
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: 6 May 1945 | Statement: [Last Post ceremony at the Menin Gate, resumedOn, 6 May 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resumedOn Context triple: [Last Post ceremony at the Menin Gate, resumedOn, 6 May 1945]
-
A.
resumedIn
chosen
Indicates that an activity, process, or state that was previously paused or interrupted has started again within or at a specified context, time, or location.
-
B.
resumesAfter
Indicates that an activity, process, or state starts again following a pause, interruption, or completion of another specified event.
-
C.
re-establishedOn
Indicates that a previously existing relationship, status, or entity was restored or brought back into effect on a specific date or time.
-
D.
replayedOn
Indicates that an event, performance, or recording was played again on a particular medium, platform, or channel.
-
E.
reopenedAfter
Indicates that an entity was closed or inactive and then opened or made active again following a specified prior event or time.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f02dca8881908efd73741397a207 |
completed | April 18, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.