Triple
T30134047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonnenstein killing center |
E765934
|
entity |
| Predicate | methodOfBodyDisposal |
P52149
|
FINISHED |
| Object | cremation |
—
|
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: cremation | Statement: [Sonnenstein killing center, methodOfBodyDisposal, cremation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfBodyDisposal Context triple: [Sonnenstein killing center, methodOfBodyDisposal, cremation]
-
A.
methodOfDisposal
chosen
Indicates the specific way or process by which something is discarded, eliminated, or otherwise gotten rid of.
-
B.
bodyDisposedBy
Indicates that a body is disposed of, handled, or gotten rid of by a particular agent or entity.
-
C.
bodyDisposedIn
Indicates that a body (typically a dead organism or corpse) is placed, discarded, or otherwise disposed of within a particular location or container.
-
D.
disposalPattern
Indicates how an entity is typically discarded, removed, or otherwise gotten rid of after its use or relevance has ended.
-
E.
abolishesBody
Indicates that one entity formally ends, eliminates, or does away with another entity or institutional body.
- 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_69f22477d1a081908df2b7e6ed16859d |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 29, 2026, 7:15 p.m.