Triple
T4211560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Anglin |
E93912
|
entity |
| Predicate | mannerOfEscape |
P19454
|
FINISHED |
| Object | never officially confirmed as dead or alive |
—
|
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 confirmed as dead or alive | Statement: [John Anglin, mannerOfEscape, never officially confirmed as dead or alive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mannerOfEscape Context triple: [John Anglin, mannerOfEscape, never officially confirmed as dead or alive]
-
A.
crewEscapeCapability
Indicates that an entity has the capability or provision for its crew to escape safely in an emergency situation.
-
B.
helpedEscape
Indicates that one entity assisted another in getting away from confinement, danger, or pursuit.
-
C.
evacuationMethod
Indicates the means or procedure by which people or objects are removed from a place of danger or risk.
-
D.
methodOfDisappearance
chosen
Indicates the specific way or process by which an entity ceases to be present, visible, or existent.
-
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_69b3451743608190808f41d17ccf2650 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e098da881909a0cc339cc186627 |
completed | March 12, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69b347efd9b08190bb50f82e4e7fe06d |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:04 p.m.