Triple
T17599260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rookwood Cemetery |
E428650
|
entity |
| Predicate | containsWarGravesOf |
P128172
|
FINISHED |
| Object | Commonwealth service 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 service personnel | Statement: [Rookwood Cemetery, containsWarGravesOf, Commonwealth service personnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsWarGravesOf Context triple: [Rookwood Cemetery, containsWarGravesOf, Commonwealth service personnel]
-
A.
hasMassGraveOf
Indicates that a location or site contains a mass grave in which the referenced individuals or remains are buried.
-
B.
hasWarGravesMaintainedBy
Indicates that one entity contains war graves whose upkeep and preservation are carried out by another entity.
-
C.
hasMassGraves
Indicates that a location or entity contains or is associated with one or more mass graves.
-
D.
hasGraveOrMemorialOf
Indicates that a location or object serves as the grave or memorial site dedicated to a particular person or entity.
-
E.
formerGraveOf
Indicates that a location once served as the grave of an entity, but no longer does (e.g., the remains have been moved or the grave has been removed).
- F. None of above. chosen
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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c474e5481909d2736241b592dab |
completed | April 19, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb50b448190a59dd4be33c76db7 |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:51 a.m.