Triple
T9365035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vimy, France |
E225377
|
entity |
| Predicate | commemoratesAtSite |
P500
|
FINISHED |
| Object | Canadian soldiers of World War I |
—
|
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: Canadian soldiers of World War I | Statement: [Vimy, France, commemoratesAtSite, Canadian soldiers of World War I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commemoratesAtSite Context triple: [Vimy, France, commemoratesAtSite, Canadian soldiers of World War I]
-
A.
commemoratedIn
Indicates that something is honored, remembered, or recognized within a particular work, event, place, or medium.
-
B.
commemoratedBy
chosen
Indicates that something is honored, remembered, or celebrated through a particular action, event, object, or representation.
-
C.
placeOfEventCommemorated
Indicates the location where the event being commemorated actually took place.
-
D.
commemoratedOn
Indicates that something is remembered, honored, or celebrated on a specific date or occasion.
-
E.
commemoratesCity
Indicates that something serves as a memorial or tribute specifically to a particular city.
- 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_69ca842cbddc819099d71ecec48cf9e5 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd503fd7f081909655e2a880c84834 |
completed | April 1, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69cc7a6abb8c81908c7a2f4ee92cc949 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:43 p.m.