Triple
T36954995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peppermint (Hi-Fi Rush) |
E914166
|
entity |
| Predicate | supportsGameplayMechanic |
—
|
GENERATED |
| Object | tag-team attacks |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsGameplayMechanic Context triple: [Peppermint (Hi-Fi Rush), supportsGameplayMechanic, tag-team attacks]
-
A.
gameplayMechanic
chosen
Indicates a relationship where one entity functions as a rule, system, or interactive feature that defines how another entity can be played or operated within a game.
-
B.
supportsGames
Indicates that an entity is capable of running, handling, or being compatible with one or more games.
-
C.
supportsGameEngine
Indicates that one entity provides compatibility, functionality, or resources necessary for the operation or integration of a particular game engine.
-
D.
supportsGameStyle
Indicates that one entity is compatible with or able to accommodate a particular game style or mode of play.
-
E.
hasGameSystem
Indicates that an item, product, or context is associated with or supports a particular game system or rules framework.
- F. None of above.
Provenance (1 batch)
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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.