Triple
T6035517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hjalmar Schacht |
E134409
|
entity |
| Predicate | laterImprisonedBy |
P11389
|
FINISHED |
| Object | denazification court in Germany |
—
|
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: denazification court in Germany | Statement: [Hjalmar Schacht, laterImprisonedBy, denazification court in Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterImprisonedBy Context triple: [Hjalmar Schacht, laterImprisonedBy, denazification court in Germany]
-
A.
hasBeenImprisonedBy
chosen
Indicates that one entity has been confined or incarcerated under the authority or control of another entity.
-
B.
wasImprisonedIn
Indicates that an entity was held in confinement or incarcerated at a particular place or facility.
-
C.
imprisonedFor
Indicates that one entity is held in detention or jail as a consequence of, or in connection with, a specific reason, action, or offense committed by another entity or itself.
-
D.
imprisonedWith
Indicates that two entities are confined or held in prison together at the same time and place.
-
E.
usedForImprisoning
Indicates that something serves as a means, tool, or method for confining or detaining someone against their will.
- 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_69c00875db5c819099dd5bb833ec43c2 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056b4e3ec819089b2d119ea2953fe |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.