Triple
T15465588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boost Mode |
E372022
|
entity |
| Predicate | supportsPlayerRole |
P10797
|
FINISHED |
| Object | GamePad player |
—
|
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: GamePad player | Statement: [Boost Mode, supportsPlayerRole, GamePad player]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPlayerRole Context triple: [Boost Mode, supportsPlayerRole, GamePad player]
-
A.
supportsPlayer
Indicates that one entity provides assistance, resources, or backing to a player in achieving their goals or performing actions.
-
B.
supportsPlayers
Indicates that an entity provides compatibility or functionality for one or more players to participate or be used.
-
C.
supportsRole
chosen
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to perform or occupy a specific role.
-
D.
associatedPlayerRole
Indicates a relationship where a specific role or function is linked to, or held by, a particular player.
-
E.
supportsPowerRoleSwap
Indicates that one entity allows or enables the exchange of power-related roles or responsibilities between participating entities.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f680cec8190836a5ec841dee224 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:33 a.m.