Triple
T6553499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otto Skorzeny |
E152384
|
entity |
| Predicate | escape |
P54365
|
FINISHED |
| Object | escaped Allied internment in 1948 |
—
|
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: escaped Allied internment in 1948 | Statement: [Otto Skorzeny, escape, escaped Allied internment in 1948]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: escape Context triple: [Otto Skorzeny, escape, escaped Allied internment in 1948]
-
A.
escapeLocation
Indicates that an entity moves away from or leaves a location to avoid danger, capture, or an undesirable situation.
-
B.
escapeAttempt
Indicates an action where an entity tries to get away from confinement, control, or a restricting situation.
-
C.
escapeStatus
chosen
Indicates whether an entity has escaped, is in the process of escaping, or has not escaped from a given situation or confinement.
-
D.
helpedEscape
Indicates that one entity assisted another in getting away from confinement, danger, or pursuit.
-
E.
coEscapee
Indicates that two or more entities escaped together from the same place or situation.
- 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_69c688058d6881908c19b309cc55dbfa |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c1b15d3481908ae66e3d7564b352 |
completed | March 27, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c6acf6d4148190914b19e9affd8c76 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:51 p.m.