Triple
T31401935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stockholms blodbad |
E801016
|
entity |
| Predicate | bodiesDisposal |
P163146
|
FINISHED |
| Object | bodies were later burned outside the city walls |
—
|
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: bodies were later burned outside the city walls | Statement: [Stockholms blodbad, bodiesDisposal, bodies were later burned outside the city walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodiesDisposal Context triple: [Stockholms blodbad, bodiesDisposal, bodies were later burned outside the city walls]
-
A.
abolishesBody
Indicates that one entity formally ends, eliminates, or does away with another entity or institutional body.
-
B.
bodiesExhumed
Indicates that previously buried bodies have been dug up and removed from their place of interment.
-
C.
disposes
chosen
Indicates that one entity discards, gets rid of, or eliminates another entity or resource.
-
D.
usedForBurialOf
Indicates that something serves or is employed as a means, place, or object for burying a particular entity.
-
E.
rescuesBodyOf
Indicates that one entity retrieves and brings to safety the body of another entity from a dangerous or inaccessible situation.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:20 p.m.