Triple
T20713042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Freeze: Reverse Blast |
E509094
|
entity |
| Predicate | trainDirection |
P120426
|
FINISHED |
| Object | backward during launch |
—
|
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: backward during launch | Statement: [Mr. Freeze: Reverse Blast, trainDirection, backward during launch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trainDirection Context triple: [Mr. Freeze: Reverse Blast, trainDirection, backward during launch]
-
A.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
B.
trainNumberDirection
Indicates the specific direction in which a train, identified by its train number, is traveling or scheduled to travel.
-
C.
terminusDirection
Indicates the directional orientation or endpoint direction associated with a route, path, or line.
-
D.
railwayTrafficDirection
Indicates the customary side of the track on which trains are operated or expected to run within a given railway system or segment.
-
E.
railwayRouteDirection
chosen
Indicates the direction or orientation in which a railway route runs or is intended to be traveled.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1ce84e48190922db93ed4b5d21b |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:15 p.m.