Triple
T5045869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Templeux-le-Guérard British Cemetery |
E113660
|
entity |
| Predicate | usedForBurialsOf |
P25159
|
FINISHED |
| Object | Commonwealth military 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: Commonwealth military personnel | Statement: [Templeux-le-Guérard British Cemetery, usedForBurialsOf, Commonwealth military personnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForBurialsOf Context triple: [Templeux-le-Guérard British Cemetery, usedForBurialsOf, Commonwealth military personnel]
-
A.
usedForBurialOf
chosen
Indicates that something serves or is employed as a means, place, or object for burying a particular entity.
-
B.
usedAsGraveUntil
Indicates that something continued to function or be designated as a grave up to a specified point in time.
-
C.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
-
D.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
E.
hasTypeOfBurial
Indicates the specific kind or method of burial associated with an entity.
- 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73fe99688190961708f5d8eb6bff |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71529d608190a53470ba6c14bb1d |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.