Triple
T21049832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volksgerichtshof |
E518546
|
entity |
| Predicate | usedPenalty |
P139991
|
FINISHED |
| Object | death penalty |
—
|
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: death penalty | Statement: [Volksgerichtshof, usedPenalty, death penalty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedPenalty Context triple: [Volksgerichtshof, usedPenalty, death penalty]
-
A.
supportsPenalty
Indicates that one entity endorses, approves of, or is in favor of a particular penalty being applied to another entity or situation.
-
B.
defaultPenalty
Indicates that a standard or automatically applied penalty is imposed in the absence of a specific or overridden penalty.
-
C.
penaltyAppliesTo
chosen
Indicates that a specific penalty is imposed on, or is relevant to, a particular entity or situation.
-
D.
penaltyPoints
Indicates that a certain number of negative points or demerits are assigned to an entity as a consequence of a rule violation, error, or infraction.
-
E.
convertedPenaltyIn
Indicates that a player successfully scored a goal by converting a penalty kick in a particular match or context.
- 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_69e0b5053ac48190921529544959e906 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fd7a5cf48190939aefaa44db1ddb |
completed | April 21, 2026, 4:30 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:34 p.m.