Triple
T33570366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dead Space |
E859879
|
entity |
| Predicate | metacriticScorePlayStation3 |
P40660
|
FINISHED |
| Object | 89 |
—
|
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: 89 | Statement: [Dead Space, metacriticScorePlayStation3, 89]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metacriticScorePlayStation3 Context triple: [Dead Space, metacriticScorePlayStation3, 89]
-
A.
metacriticPlatform
Indicates the platform (such as console, PC, or device) on which a work is evaluated or listed in Metacritic.
-
B.
metacriticCategory
Indicates that one entity is classified under a specific Metacritic-defined category (such as a media type, genre, or section) in the Metacritic system.
-
C.
metacriticReception
Indicates the critical reception or review score an entity received on Metacritic.
-
D.
hasMetacriticId
Indicates that an entity is associated with a specific identifier used by Metacritic to reference it in their database.
-
E.
hasMetascore
chosen
Indicates that an entity is associated with a Metascore rating, typically representing an aggregated critical review score.
- 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_69f6f744799c8190b02ac37eca254ccd |
completed | May 3, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:40 a.m.