Triple
T32510139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomb Raider (2013 video game) |
E830907
|
entity |
| Predicate | DefinitiveEditionReleasePlatform |
P182055
|
FINISHED |
| Object | PlayStation 4 |
—
|
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: PlayStation 4 | Statement: [Tomb Raider (2013 video game), DefinitiveEditionReleasePlatform, PlayStation 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DefinitiveEditionReleasePlatform Context triple: [Tomb Raider (2013 video game), DefinitiveEditionReleasePlatform, PlayStation 4]
-
A.
anniversaryEditionPlatform
Indicates the platform or system on which an anniversary edition of a work is released or made available.
-
B.
remasteredVersionPlatform
chosen
Indicates that a remastered version of a work is available on, or associated with, a particular platform.
-
C.
appearsInPlatform
Indicates that an entity is present, available, or featured within a particular platform or system.
-
D.
adaptationReleasePlatform
Indicates the platform or medium on which an adaptation is released or made available.
-
E.
occursOnPlatform
Indicates that an event, action, or process takes place or is carried out on a specified platform.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: May 1, 2026, 1 a.m.