Triple
T8814277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PlayStation VR2 |
E209738
|
entity |
| Predicate | headsetHapticsLocation |
P84757
|
FINISHED |
| Object | forehead area |
—
|
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: forehead area | Statement: [PlayStation VR2, headsetHapticsLocation, forehead area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headsetHapticsLocation Context triple: [PlayStation VR2, headsetHapticsLocation, forehead area]
-
A.
peripheralType
Indicates the specific category or kind of peripheral device associated with or used by an entity.
-
B.
hasBluetooth
Indicates that one entity is equipped with or supports Bluetooth connectivity.
-
C.
locationInSystem
Indicates that one entity is situated within or belongs to the spatial or organizational bounds of a particular system.
-
D.
wearerDevice
Indicates that a device is worn or carried by a particular entity (the wearer).
-
E.
seatLocation
Indicates the spatial position or placement of a seat relative to a reference point or environment.
- F. None of above. chosen
Provenance (4 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ff1a4448190b5559f440d264442 |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c21e64c81908490e3b0875dc0d6 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:45 p.m.