Triple
T32583256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rise of the Tomb Raider |
E832847
|
entity |
| Predicate | initialPlatforms |
P39167
|
FINISHED |
| Object | Xbox One |
—
|
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: Xbox One | Statement: [Rise of the Tomb Raider, initialPlatforms, Xbox One]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialPlatforms Context triple: [Rise of the Tomb Raider, initialPlatforms, Xbox One]
-
A.
hadPlatforms
Indicates that something was equipped with or featured one or more platforms.
-
B.
platforms
Indicates that one entity provides or serves as a base, medium, or environment that supports the operation, distribution, or presentation of another entity.
-
C.
earlyPlatformFor
Indicates that one entity served as an initial or precursor platform, environment, or venue enabling the development, exposure, or operation of another entity.
-
D.
platformsDevelopedFor
chosen
Indicates the platforms (e.g., operating systems, devices, or environments) for which something has been specifically created or adapted.
-
E.
coveredPlatform
Indicates that a platform is sheltered by a roof or overhead structure, providing cover from above.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 1, 2026, 1:04 a.m.