Triple
T335510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berghof |
E6715
|
entity |
| Predicate | destructionContext |
P5325
|
FINISHED |
| Object | post-World War II denazification |
—
|
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: post-World War II denazification | Statement: [Berghof, destructionContext, post-World War II denazification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destructionContext Context triple: [Berghof, destructionContext, post-World War II denazification]
-
A.
demolished
Indicates that one entity completely destroyed or razed another entity, typically a structure or object, so that it no longer exists in its previous form.
-
B.
hasCauseOfDestruction
chosen
Indicates that one entity is the cause or agent responsible for the destruction or damage of another entity.
-
C.
dateDestroyed
Indicates the specific date on which an entity was destroyed or ceased to exist.
-
D.
closureContext
Indicates the surrounding scope or environment in which an operation, expression, or function is defined and executed, capturing the variables and bindings available to it.
-
E.
releaseContext
Indicates ending or relinquishing a previously established context or state associated with an interaction or process.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eac81c0c8190b3cb0d53b1cf62b5 |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94f049881908f10bb6548a8bb2e |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.