Triple
T34788893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanns-Martin Schleyer |
E1002886
|
entity |
| Predicate | kidnappingContext |
P165557
|
FINISHED |
| Object | German Autumn |
—
|
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: German Autumn | Statement: [Hanns-Martin Schleyer, kidnappingContext, German Autumn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kidnappingContext Context triple: [Hanns-Martin Schleyer, kidnappingContext, German Autumn]
-
A.
wasKidnapped
Indicates that an entity was forcibly taken and held against their will by another entity.
-
B.
kidnappedIn
Indicates that an entity was forcibly taken or abducted within, or as part of an event occurring in, a specified location or context.
-
C.
oftenKidnaps
Indicates that one entity frequently or habitually kidnaps another entity.
-
D.
kidnappingIsCentralPlot
Indicates that a kidnapping is the main driving event or focus of the story’s plot.
-
E.
abductionContext
chosen
Indicates a contextual relationship in which an abduction event occurs, specifying the surrounding circumstances, conditions, or setting of that abduction.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.