Triple
T36853354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PlayStation Move Heroes |
E910726
|
entity |
| Predicate | publisherPlatformBrand |
P162646
|
FINISHED |
| Object | PlayStation |
—
|
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 | Statement: [PlayStation Move Heroes, publisherPlatformBrand, PlayStation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherPlatformBrand Context triple: [PlayStation Move Heroes, publisherPlatformBrand, PlayStation]
-
A.
parentPlatformCompany
Indicates that one company serves as the overarching or owning platform company for another company within a corporate or business structure.
-
B.
publishingPlatform
Indicates that one entity serves as the medium or service through which another entity is published or made publicly available.
-
C.
successorPlatformBrand
Indicates that one platform brand directly follows and replaces another in a product or generational sequence.
-
D.
brandOrPortal
chosen
Indicates that one entity functions as a brand or a branded portal associated with another entity.
-
E.
mediaBrandOf
Indicates that a media outlet, channel, or publication is the brand associated with or responsible for a given piece of media content or product.
- 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffb97b8ff8819088b105d99a0820c9 |
completed | May 9, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69ffb88ef7388190a710120ed76edc0e |
completed | May 9, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.