Triple
T23099970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phantom Zone |
E575997
|
entity |
| Predicate | escapePossibility |
P150914
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Phantom Zone, escapePossibility, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: escapePossibility Context triple: [Phantom Zone, escapePossibility, yes]
-
A.
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.
-
B.
escapeStatus
Indicates whether an entity has escaped, is in the process of escaping, or has not escaped from a given situation or confinement.
-
C.
escapeAttempt
Indicates an action where an entity tries to get away from confinement, control, or a restricting situation.
-
D.
escapeMechanism
Indicates a means or method by which an entity avoids, evades, or breaks free from a threat, constraint, or controlling influence.
-
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. 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_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. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 3:58 p.m.