Triple
T8761128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amon Göth |
E208199
|
entity |
| Predicate | deathSentence |
P20881
|
FINISHED |
| Object | 1946 |
—
|
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: 1946 | Statement: [Amon Göth, deathSentence, 1946]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathSentence Context triple: [Amon Göth, deathSentence, 1946]
-
A.
deathPenaltyImposedFor
Indicates that a death penalty has been officially assigned as the punishment for a particular offense or action.
-
B.
numberSentencedToDeath
Indicates the number of individuals who have been formally sentenced to receive the death penalty.
-
C.
timeOfCondemnation
Indicates the specific time at which a condemnation (such as a legal judgment or formal denunciation) occurs or is issued.
-
D.
deathPeninsula
Indicates a relationship where a death occurs on, near, or in association with a specific peninsula.
-
E.
sentencedTo
chosen
Indicates that an authority has officially assigned a specific punishment or penalty to an entity, typically as the outcome of a legal or disciplinary process.
- 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_69ca835df7e08190ac875664cca8f9ca |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5df9729481908679151988b76d2f |
completed | March 31, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1884bc8190a46e8308db31f7ab |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:40 p.m.