Triple
T21049821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volksgerichtshof |
E518546
|
entity |
| Predicate | handledCaseType |
P4217
|
FINISHED |
| Object | high treason |
—
|
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: high treason | Statement: [Volksgerichtshof, handledCaseType, high treason]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handledCaseType Context triple: [Volksgerichtshof, handledCaseType, high treason]
-
A.
handledHighProfileCase
Indicates that an entity has been responsible for managing or working on a case that is considered high-profile or widely notable.
-
B.
handledWith
Indicates that an entity is managed, processed, or dealt with using a particular method, tool, or means.
-
C.
hasTypeOfCase
chosen
Indicates that an entity is associated with or classified under a particular type or category of case.
-
D.
handledIn
Indicates that an action, request, or process is managed, processed, or resolved within a particular context, location, system, or jurisdiction.
-
E.
handlesOperationType
Indicates that an entity is responsible for processing or managing a specific type or category of operation.
- 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.