Triple
T29461918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National War Memorial, Ottawa |
E747259
|
entity |
| Predicate | hasGuardOfHonour |
P158792
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [National War Memorial, Ottawa, hasGuardOfHonour, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGuardOfHonour Context triple: [National War Memorial, Ottawa, hasGuardOfHonour, yes]
-
A.
hasRollOfHonour
Indicates that an entity maintains or is associated with a formal record listing individuals who have received honors, awards, or recognition.
-
B.
ceremonialGunSalute
Indicates a formal military or state honor in which guns are fired in a prescribed sequence to ceremonially recognize or pay respect to a person, event, or occasion.
-
C.
burialHonors
Indicates a relationship where an entity is recognized or commemorated with special respect or distinction in the context of their burial or interment.
-
D.
honourOf
Indicates that one entity is the source, bearer, or cause of another entity’s honor, prestige, or distinguished recognition.
-
E.
hasHonorGuard
chosen
Indicates that an entity is accompanied, protected, or ceremonially attended by an honor guard.
- 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_69f0bd4125f88190b56104591351619c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66ba455e0819092aaa13310599a71 |
completed | May 2, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 3:50 p.m.