Triple
T31490189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berghof sanatorium |
E803384
|
entity |
| Predicate | temporalEffectOnCharacters |
P176353
|
FINISHED |
| Object | distorted sense of time |
—
|
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: distorted sense of time | Statement: [Berghof sanatorium, temporalEffectOnCharacters, distorted sense of time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporalEffectOnCharacters Context triple: [Berghof sanatorium, temporalEffectOnCharacters, distorted sense of time]
-
A.
temporalEffect
Indicates a relationship where one event, state, or action produces consequences or changes that occur at a later time.
-
B.
temporaryEffect
Indicates that one entity causes or experiences an effect that is limited in duration and does not produce a lasting change.
-
C.
narrativeEffect
Indicates how one event, action, or element in a story influences the progression, tone, or interpretation of the overall narrative.
-
D.
eventEffect
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
-
E.
tempoCharacter
Indicates the characteristic speed or pacing quality associated with an action, event, or process.
- F. None of above. chosen
Provenance (4 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6dfcafd0c81908d86662948c539d6 |
completed | May 3, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6df418f488190a5e7ff41f32dceda |
completed | May 3, 2026, 5:38 a.m. |
Created at: April 30, 2026, 9:37 p.m.