Triple
T16105590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charley Butts |
E390729
|
entity |
| Predicate | reasonForFailedEscape |
P77548
|
FINISHED |
| Object | loses nerve and stays behind |
—
|
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: loses nerve and stays behind | Statement: [Charley Butts, reasonForFailedEscape, loses nerve and stays behind]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForFailedEscape Context triple: [Charley Butts, reasonForFailedEscape, loses nerve and stays behind]
-
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.
escapeAttempt
Indicates an action where an entity tries to get away from confinement, control, or a restricting situation.
-
C.
reasonForException
Indicates the specific cause or justification for why a normal rule, process, or condition does not apply in a given case.
-
D.
failureCause
chosen
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
-
E.
fledDueTo
Indicates that one entity escaped or ran away because of, or in response to, another entity or specific cause.
- 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.