Triple
T4715275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leon Feldhendler |
E104620
|
entity |
| Predicate | afterEscape |
P59130
|
FINISHED |
| Object | lived in hiding in Lublin |
—
|
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: lived in hiding in Lublin | Statement: [Leon Feldhendler, afterEscape, lived in hiding in Lublin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterEscape Context triple: [Leon Feldhendler, afterEscape, lived in hiding in Lublin]
-
A.
escapeStatus
Indicates whether an entity has escaped, is in the process of escaping, or has not escaped from a given situation or confinement.
-
B.
escapeBehavior
Indicates a relationship where an entity actively attempts to avoid, flee from, or get away from another entity, situation, or constraint.
-
C.
afterRelease
Indicates that one event, action, or state occurs subsequent to the release of another entity or condition.
-
D.
coEscapee
Indicates that two or more entities escaped together from the same place or situation.
-
E.
escapeAttempt
Indicates an action where an entity tries to get away from confinement, control, or a restricting situation.
- F. None of above. chosen
Provenance (4 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_69bd43ec4a348190bc41afae43375e71 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd680b06e881908de87edf815f3cc0 |
completed | March 20, 2026, 3:30 p.m. |
Created at: March 20, 2026, 1:18 p.m.