Triple
T31946193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R1 button |
E815656
|
entity |
| Predicate | supportsSystemRemap |
P13398
|
FINISHED |
| Object | PlayStation 4 |
E42441
|
NE 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: PlayStation 4 | Statement: [R1 button, supportsSystemRemap, PlayStation 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSystemRemap Context triple: [R1 button, supportsSystemRemap, PlayStation 4]
-
A.
supportsEnvironmentMapping
Indicates that one entity provides or enables environment mapping functionality for another entity or context.
-
B.
supportedSystem
chosen
Indicates that one entity provides compatibility, functionality, or operational support for another system.
-
C.
supportsUpdateSystem
Indicates that an entity is capable of performing or handling operations to modify or upgrade a system.
-
D.
supportsMigrationOf
Indicates that one entity enables, facilitates, or is compatible with the migration or transfer of another entity from one environment, system, or context to another.
-
E.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
- F. None of above.
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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2e8a484aa48190a02fa1d469a1ed15 |
completed | June 14, 2026, 11:02 a.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:06 a.m.