Triple
T37610835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vanquish |
E935778
|
entity |
| Predicate | bundlePlatform |
P5090
|
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: [Vanquish, bundlePlatform, PlayStation 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bundlePlatform Context triple: [Vanquish, bundlePlatform, PlayStation 4]
-
A.
platforms
Indicates that one entity provides or serves as a base, medium, or environment that supports the operation, distribution, or presentation of another entity.
-
B.
worksOnPlatform
Indicates that an entity performs its functions, operations, or activities using or within a specified platform.
-
C.
supportedPlatform
chosen
Indicates that one entity (such as a system, application, or service) is compatible with and can operate on a particular platform.
-
D.
launchPlatformName
Indicates the name of the platform or site from which a launch (typically of a vehicle, rocket, or mission) is conducted.
-
E.
isKeyPlatformFor
Indicates that one entity serves as a primary or foundational platform that enables, supports, or underpins the activities, services, or operations of another entity.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.