Triple

T13240857
Position Surface form Disambiguated ID Type / Status
Subject Commonwealth war cemeteries E315274 entity
Predicate administersGravesOf P38888 FINISHED
Object British armed forces personnel 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: British armed forces personnel | Statement: [Commonwealth war cemeteries, administersGravesOf, British armed forces personnel]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: administersGravesOf
Context triple: [Commonwealth war cemeteries, administersGravesOf, British armed forces personnel]
  • A. hasGraveOrMemorialOf
    Indicates that a location or object serves as the grave or memorial site dedicated to a particular person or entity.
  • B. hasMassGraveOf
    Indicates that a location or site contains a mass grave in which the referenced individuals or remains are buried.
  • C. isCemeteryFor chosen
    Indicates that one entity serves as the burial ground designated for another entity, such as a community, group, or location.
  • D. hasGravesOfCitizenship
    Indicates that a place contains graves belonging to individuals of a specified citizenship.
  • E. cemeteryKnownFor
    Indicates that a cemetery is notable or recognized for a particular person, event, feature, or characteristic.
  • 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_69d806b1072881909e46bd212259c5f0 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98d5850ac8190849a51da39efe5be completed April 10, 2026, 11:52 p.m.
PD Predicate disambiguation batch_69d98bcb21648190aef241de1e7887e2 completed April 10, 2026, 11:46 p.m.
Created at: April 9, 2026, 9:23 p.m.