Triple
T31264619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolfsschanze |
E797217
|
entity |
| Predicate | targetOfAssassinationAttemptBy |
P8557
|
FINISHED |
| Object | Claus von Stauffenberg |
—
|
NE NERFINISHED |
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: Claus von Stauffenberg | Statement: [Wolfsschanze, targetOfAssassinationAttemptBy, Claus von Stauffenberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetOfAssassinationAttemptBy Context triple: [Wolfsschanze, targetOfAssassinationAttemptBy, Claus von Stauffenberg]
-
A.
wasAssassinationTarget
Indicates that an entity was the intended victim or objective of an assassination attempt.
-
B.
wasAssassinatedIn
Indicates that an entity was killed in a deliberate, targeted assassination that occurred at a specific place or time.
-
C.
assassinationOrganizedBy
Indicates that an assassination was planned, directed, or coordinated by a particular agent or organization.
-
D.
assassinationAttemptLocation
chosen
Indicates the place where an attempted assassination occurred or was intended to occur.
-
E.
assassinatedIn
Indicates that an assassination of one entity occurred within the specified location or context represented by 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: April 29, 2026, 9:12 p.m.