Triple
T23099972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phantom Zone |
E575997
|
entity |
| Predicate | escapeConsequence |
P104894
|
FINISHED |
| Object | release of dangerous Kryptonian criminals |
—
|
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: release of dangerous Kryptonian criminals | Statement: [Phantom Zone, escapeConsequence, release of dangerous Kryptonian criminals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: escapeConsequence Context triple: [Phantom Zone, escapeConsequence, release of dangerous Kryptonian criminals]
-
A.
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.
-
B.
avoidedConsequence
Indicates that an action or event prevented a particular consequence from occurring.
-
C.
escapeMechanism
Indicates a means or method by which an entity avoids, evades, or breaks free from a threat, constraint, or controlling influence.
-
D.
unexpectedConsequenceOf
Indicates that one event, action, or condition occurs as an unforeseen or unintended result of another.
-
E.
escapeBehavior
Indicates a relationship where an entity actively attempts to avoid, flee from, or get away from another entity, situation, or constraint.
- 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_69e245c060b48190a9bd61a47a16db17 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18de81060819084ab618f05aae583 |
completed | April 29, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:58 p.m.