Triple
T29854596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PlayStation VR |
E758150
|
entity |
| Predicate | processingUnit |
P125913
|
FINISHED |
| Object | external processor box |
—
|
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: external processor box | Statement: [PlayStation VR, processingUnit, external processor box]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: processingUnit Context triple: [PlayStation VR, processingUnit, external processor box]
-
A.
hasProcessingUnits
chosen
Indicates that an entity is equipped with or contains one or more processing units (such as CPUs, GPUs, or similar computational components).
-
B.
executionUnits
Indicates a relationship where a process, task, or operation is carried out by one or more specific execution units (such as cores, threads, or processing elements).
-
C.
processingUse
Indicates that one entity uses or applies another entity as part of a processing or transformation activity.
-
D.
coreUnitType
Indicates that one entity is classified as the primary or fundamental type/category to which another entity (a core unit) belongs.
-
E.
componentUnit
Indicates that one entity functions as a constituent or sub-unit that forms part of a larger composite 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6764ace8881909ccba69193322eef |
completed | May 2, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 5:45 p.m.