Triple
T37550576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massive Fury Pack |
E933581
|
entity |
| Predicate | videoGameDLCFor |
P39175
|
FINISHED |
| Object | Transformers: Fall of Cybertron |
—
|
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: Transformers: Fall of Cybertron | Statement: [Massive Fury Pack, videoGameDLCFor, Transformers: Fall of Cybertron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: videoGameDLCFor Context triple: [Massive Fury Pack, videoGameDLCFor, Transformers: Fall of Cybertron]
-
A.
hasDLC
chosen
Indicates that one entity includes, is associated with, or is supplemented by another entity as downloadable content.
-
B.
DLCName
Indicates that the associated value is the name or title of a specific downloadable content (DLC) package related to the entity.
-
C.
videoGame
Indicates that one entity is a video game associated with, created by, or otherwise related to another entity.
-
D.
gameDelivery
Indicates that a game is being provided, distributed, or transferred from one party or source to another.
-
E.
relatedGame
Indicates that one game has a notable connection or association with another game, such as shared content, themes, or series.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.