Triple
T31326093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Passendale |
E798889
|
entity |
| Predicate | warCemeteryType |
P2742
|
FINISHED |
| Object | Commonwealth War Graves Commission cemetery area |
E315274
|
NE 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: Commonwealth War Graves Commission cemetery area | Statement: [Passendale, warCemeteryType, Commonwealth War Graves Commission cemetery area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warCemeteryType Context triple: [Passendale, warCemeteryType, Commonwealth War Graves Commission cemetery area]
-
A.
cemeteryType
chosen
Indicates the specific kind or classification of a cemetery associated with an entity.
-
B.
containsWarGravesOf
Indicates that a place or site includes burial locations or memorials for individuals who died in war.
-
C.
countryOfCemetery
Indicates that a cemetery is located within the territory of a specified country.
-
D.
hasWarGravesMaintainedBy
Indicates that one entity contains war graves whose upkeep and preservation are carried out by another entity.
-
E.
memorialType
Indicates the specific kind or category of memorial associated with an entity (e.g., plaque, statue, monument).
- F. None of above.
Provenance (4 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69eb1b4ac81908aa52c805d38a5c9 |
completed | May 3, 2026, 1:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2a1e4bcb9c81908072c16ff6b0a415 |
completed | June 11, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:15 p.m.