Triple
T15649890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leipzig Prison |
E376282
|
entity |
| Predicate | governmentTypeDuringNaziEra |
P74631
|
FINISHED |
| Object | totalitarian regime |
—
|
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: totalitarian regime | Statement: [Leipzig Prison, governmentTypeDuringNaziEra, totalitarian regime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentTypeDuringNaziEra Context triple: [Leipzig Prison, governmentTypeDuringNaziEra, totalitarian regime]
-
A.
countryDuringNaziPeriod
Indicates that an entity functioned as a country or national state specifically during the historical period of Nazi rule.
-
B.
legalStatusInNaziView
Indicates the legal classification or standing an entity was assigned under Nazi ideology and law.
-
C.
wasNaziEraSiteOf
Indicates that a location served as the site of specific events, activities, or functions during the Nazi era.
-
D.
politicalSystemDuringRule
chosen
Indicates the type of political system that was in place during a particular ruler’s period of governance.
-
E.
germanOccupationAuthority
Indicates that an entity functioned as an authority or administrative body in charge during the German occupation of a territory.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ed7212c8190be6ff76afa25f7ca |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:15 a.m.