Triple
T21230824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Road Cemetery, Adelaide |
E523207
|
entity |
| Predicate | hasWarGravesOf |
P128172
|
FINISHED |
| Object | Commonwealth war dead |
—
|
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 war dead | Statement: [North Road Cemetery, Adelaide, hasWarGravesOf, Commonwealth war dead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWarGravesOf Context triple: [North Road Cemetery, Adelaide, hasWarGravesOf, Commonwealth war dead]
-
A.
containsWarGravesOf
chosen
Indicates that a place or site includes burial locations or memorials for individuals who died in war.
-
B.
hasWarGravesMaintainedBy
Indicates that one entity contains war graves whose upkeep and preservation are carried out by another entity.
-
C.
hasMassGraveOf
Indicates that a location or site contains a mass grave in which the referenced individuals or remains are buried.
-
D.
hasMassGraves
Indicates that a location or entity contains or is associated with one or more mass graves.
-
E.
hasTombs
Indicates that one entity possesses, contains, or is the location of one or more tombs associated with another 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734af3d508190b3359d14496370b6 |
completed | April 21, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:45 p.m.