Triple
T33933472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hill 70 Memorial |
E869965
|
entity |
| Predicate | commemoratesForce |
P135736
|
FINISHED |
| Object | Canadian Corps |
—
|
NE NERFINISHED |
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 Corps | Statement: [Hill 70 Memorial, commemoratesForce, Canadian Corps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commemoratesForce Context triple: [Hill 70 Memorial, commemoratesForce, Canadian Corps]
-
A.
commemoratesForces
chosen
Indicates a relationship where something serves to honor or remember military or armed forces for their service or sacrifice.
-
B.
commemoratesUnit
Indicates that one entity serves as a memorial or tribute recognizing, honoring, or remembering a specific unit.
-
C.
militaryBranchCommemorated
Indicates that one entity serves to honor or memorialize a specific branch of the military.
-
D.
commemoratedFor
Indicates that one entity is honored, remembered, or celebrated because of a particular action, achievement, event, or characteristic associated with it.
-
E.
commemoratesCommander
Indicates that one entity serves to honor or remember a specific military commander.
- 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_69f3499a59788190bff762a891471b31 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 1, 2026, 1:49 a.m.