Triple
T35289732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steven Stayner |
E1019187
|
entity |
| Predicate | escapedWith |
P121340
|
FINISHED |
| Object | Timothy White |
—
|
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: Timothy White | Statement: [Steven Stayner, escapedWith, Timothy White]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: escapedWith Context triple: [Steven Stayner, escapedWith, Timothy White]
-
A.
escapedBy
Indicates that an entity is freed or enabled to escape through the actions or intervention of another entity.
-
B.
escapedTo
Indicates that an entity fled or broke free from a place, situation, or captor and reached another location as a result.
-
C.
escapeOf
Indicates that one entity escapes, is released, or leaks out from another entity or containing context.
-
D.
escapesWith
chosen
Indicates that one entity flees or breaks free from a situation, place, or constraint together with another entity as a companion or accomplice.
-
E.
escapesAs
Indicates that one entity leaves or breaks free from another entity or situation, typically to avoid capture, danger, or constraint.
- 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.