Triple
T16105552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Lee Morris |
E390728
|
entity |
| Predicate | escapeResult |
P104894
|
FINISHED |
| Object | never officially found |
—
|
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: never officially found | Statement: [Frank Lee Morris, escapeResult, never officially found]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: escapeResult Context triple: [Frank Lee Morris, escapeResult, never officially found]
-
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.
escapeOutcome
chosen
Indicates the result or consequence of an attempt to escape, such as whether it succeeded, failed, or led to a particular follow-up state.
-
C.
escapeMechanism
Indicates a means or method by which an entity avoids, evades, or breaks free from a threat, constraint, or controlling influence.
-
D.
escapeBehavior
Indicates a relationship where an entity actively attempts to avoid, flee from, or get away from another entity, situation, or constraint.
-
E.
escapeLocation
Indicates that an entity moves away from or leaves a location to avoid danger, capture, or an undesirable 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.