Triple
T13649587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dora Trial at Dachau |
E326693
|
entity |
| Predicate | verdictsIncluded |
P93123
|
FINISHED |
| Object | death sentences |
—
|
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 sentences | Statement: [Dora Trial at Dachau, verdictsIncluded, death sentences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verdictsIncluded Context triple: [Dora Trial at Dachau, verdictsIncluded, death sentences]
-
A.
verdict
Indicates the formal decision or judgment reached and declared at the conclusion of a legal or evaluative process.
-
B.
judgmentInvolves
Indicates that a particular judgment, decision, or legal ruling includes, concerns, or pertains to a specified entity or matter.
-
C.
containsJudgmentIn
chosen
Indicates that one entity includes or embeds a specific judgment or decision within it.
-
D.
includesDecisionsBy
Indicates that something contains, encompasses, or takes into account decisions made by a specified party or set of parties.
-
E.
includesDecisionOn
Indicates that one item or process contains, encompasses, or explicitly addresses a particular decision or determination.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc608466c81908f6d2c9c92cc86aa |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:52 p.m.