Triple
T26757952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exilliteratur |
E674724
|
entity |
| Predicate | zentralerZeitraum |
P302
|
FINISHED |
| Object | 1933–1945 |
—
|
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: 1933–1945 | Statement: [Exilliteratur, zentralerZeitraum, 1933–1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zentralerZeitraum Context triple: [Exilliteratur, zentralerZeitraum, 1933–1945]
-
A.
timePeriodAsCenterUntil
Indicates that a time period is considered the central reference point and extends up to, but not beyond, a specified endpoint in time.
-
B.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
C.
timePeriodFormulated
Indicates the time period during which something (such as a concept, theory, or plan) was formulated or developed.
-
D.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
-
E.
centralAttackPeriod
Indicates the time interval during which a central or primary attack is actively occurring or at its peak intensity.
- 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f618d6dad48190b2bcb3ddf080dadf |
completed | May 2, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:56 a.m.