Triple
T16847968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snake Plissken |
E409593
|
entity |
| Predicate | missionInEscapeFromLA |
P125093
|
FINISHED |
| Object | retrieve a doomsday device |
—
|
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: retrieve a doomsday device | Statement: [Snake Plissken, missionInEscapeFromLA, retrieve a doomsday device]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionInEscapeFromLA Context triple: [Snake Plissken, missionInEscapeFromLA, retrieve a doomsday device]
-
A.
escapeLocation
Indicates that an entity moves away from or leaves a location to avoid danger, capture, or an undesirable situation.
-
B.
escapeOutcome
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.
lostCity
Indicates that a city once known or inhabited has disappeared, been destroyed, or can no longer be located.
-
D.
crewEscapeCapability
Indicates that an entity has the capability or provision for its crew to escape safely in an emergency situation.
-
E.
launchEscapeSystem
Indicates initiating or activating an emergency mechanism designed to rapidly propel occupants or payload away from a vehicle or structure to ensure their safety.
- F. None of above. chosen
Provenance (4 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b376bac48190ae09f29a28c55f8c |
completed | April 18, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e34fb7c8c8819086975b7955b7d8ef |
completed | April 18, 2026, 9:32 a.m. |
Created at: April 10, 2026, 5:24 a.m.