Triple
T23583667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plötzensee Prison |
E582276
|
entity |
| Predicate | executionMethods |
P106448
|
FINISHED |
| Object | hanging |
—
|
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: hanging | Statement: [Plötzensee Prison, executionMethods, hanging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: executionMethods Context triple: [Plötzensee Prison, executionMethods, hanging]
-
A.
primaryMethodOfExecution
chosen
Indicates the method most commonly or officially used to carry out an execution.
-
B.
executionBy
Indicates that one entity carries out or performs the execution (killing or implementation of a death sentence) of another entity.
-
C.
executionEngine
Indicates the mechanism or component responsible for carrying out, managing, or running a defined process, task, or set of operations.
-
D.
executionSide
Indicates which party or side in a transaction, contract, or interaction is responsible for performing or carrying out the specified action.
-
E.
executionModel
Indicates how a process, task, or operation is carried out or implemented, specifying the underlying method, strategy, or mechanism of its execution.
- 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b02e19808190a41bce305f6cd5da |
completed | April 29, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:40 p.m.