Triple
T31490192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berghof sanatorium |
E803384
|
entity |
| Predicate | hasNarrativeAtmosphere |
P130432
|
FINISHED |
| Object | claustrophobic |
—
|
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: claustrophobic | Statement: [Berghof sanatorium, hasNarrativeAtmosphere, claustrophobic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNarrativeAtmosphere Context triple: [Berghof sanatorium, hasNarrativeAtmosphere, claustrophobic]
-
A.
hasNarrative
Indicates that one entity contains, presents, or is associated with a story or narrative about another entity or subject.
-
B.
hasNarrativeToneOfWork
chosen
Indicates that a work exhibits or is characterized by a particular narrative tone.
-
C.
narrativeEffect
Indicates how one event, action, or element in a story influences the progression, tone, or interpretation of the overall narrative.
-
D.
hasNarrativeContext
Indicates that an entity is associated with, or situated within, a particular narrative or storytelling context that frames its meaning or role.
-
E.
containsNarrativeOf
Indicates that one entity includes or presents the story, account, or narrative content of another entity.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: April 30, 2026, 9:37 p.m.