Triple
T37446922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | assassination of Giacomo Matteotti |
E930572
|
entity |
| Predicate | hasBodyDisposalMethod |
P52149
|
FINISHED |
| Object | burial in a shallow grave |
—
|
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: burial in a shallow grave | Statement: [assassination of Giacomo Matteotti, hasBodyDisposalMethod, burial in a shallow grave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBodyDisposalMethod Context triple: [assassination of Giacomo Matteotti, hasBodyDisposalMethod, burial in a shallow grave]
-
A.
bodyDisposedBy
Indicates that a body is disposed of, handled, or gotten rid of by a particular agent or entity.
-
B.
hasBodyCount
Indicates that an entity is associated with a specific number of deaths or kills.
-
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.
hasBodyOf
Indicates that one entity possesses, contains, or is composed of the physical body or main substance of another entity.
-
E.
methodOfDisposal
chosen
Indicates the specific way or process by which something is discarded, eliminated, or otherwise gotten rid of.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe72dca2f08190beff17de3d2aada6 |
completed | May 8, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69fe70bca8d08190b810e1e616ceac44 |
completed | May 8, 2026, 11:24 p.m. |
Created at: May 3, 2026, 4:17 p.m.