Triple
T31177242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canada Bereft |
E794782
|
entity |
| Predicate | locatedInCemeteryOrMemorialSite |
P18505
|
FINISHED |
| Object | Vimy Memorial Park, France |
—
|
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: Vimy Memorial Park, France | Statement: [Canada Bereft, locatedInCemeteryOrMemorialSite, Vimy Memorial Park, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCemeteryOrMemorialSite Context triple: [Canada Bereft, locatedInCemeteryOrMemorialSite, Vimy Memorial Park, France]
-
A.
locatedInCemetery
Indicates that one entity is situated within the grounds or area of a cemetery.
-
B.
memorialLocatedAt
chosen
Indicates that a memorial is situated or found at a specific location.
-
C.
isCemeteryFor
Indicates that one entity serves as the burial ground designated for another entity, such as a community, group, or location.
-
D.
locatedInTheAdministrativeTerritorialEntityOfBurial
Indicates that the place or site referenced is situated within the specified administrative territorial entity where the burial is located.
-
E.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
- 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a015ff02814819094806517fc4c69fa |
completed | May 11, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_6a0154ddd3c48190b85f9f48731cfd8f |
completed | May 11, 2026, 4:02 a.m. |
Created at: April 29, 2026, 9:08 p.m.