Triple
T16105589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charley Butts |
E390729
|
entity |
| Predicate | failsToEscape |
P113077
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Charley Butts, failsToEscape, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: failsToEscape Context triple: [Charley Butts, failsToEscape, yes]
-
A.
escapedBy
Indicates that an entity is freed or enabled to escape through the actions or intervention of another entity.
-
B.
failsTo
chosen
Indicates that an expected action, process, or condition does not successfully occur or is not fulfilled.
-
C.
escapeBehavior
Indicates a relationship where an entity actively attempts to avoid, flee from, or get away from another entity, situation, or constraint.
-
D.
escapeStatus
Indicates whether an entity has escaped, is in the process of escaping, or has not escaped from a given situation or confinement.
-
E.
escapeAttempt
Indicates an action where an entity tries to get away from confinement, control, or a restricting 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff6b91a48190a04648d4cad2c4b1 |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.