Triple
T33570362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dead Space |
E859879
|
entity |
| Predicate | hasAnimatedTieIn |
P145985
|
FINISHED |
| Object | Dead Space: Downfall |
—
|
NE NERFINISHED |
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: Dead Space: Downfall | Statement: [Dead Space, hasAnimatedTieIn, Dead Space: Downfall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnimatedTieIn Context triple: [Dead Space, hasAnimatedTieIn, Dead Space: Downfall]
-
A.
hasMerchandiseTieIn
Indicates that one entity has a commercial or promotional product or line (merchandise) that is directly tied to, branded with, or derived from another entity.
-
B.
hasSpinOffTieIns
Indicates that one entity has related derivative works or products that are spin-offs tied to another entity.
-
C.
hasAnimatedPrequel
chosen
Indicates that one work serves as an earlier, animated installment in the narrative or release sequence of another work.
-
D.
isAnimated
Indicates that an entity possesses animation, meaning it is depicted or realized through moving images rather than static or live-action form.
-
E.
isAnimatedBy
Indicates that an entity’s motion or behavior is driven, controlled, or brought to life by another entity or process.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 1, 2026, 1:40 a.m.