Triple
T35386983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warp Whistle |
E1022815
|
entity |
| Predicate | gameMechanicImpact |
P118563
|
FINISHED |
| Object | enables sequence breaking |
—
|
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: enables sequence breaking | Statement: [Warp Whistle, gameMechanicImpact, enables sequence breaking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameMechanicImpact Context triple: [Warp Whistle, gameMechanicImpact, enables sequence breaking]
-
A.
gameplayMechanic
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.
gameplayImpact
chosen
Indicates how one element in a game affects the mechanics, difficulty, or overall experience of playing that game.
-
C.
notableLevelMechanic
Indicates that an entity is recognized for its significant involvement in designing, implementing, or innovating game level mechanics.
-
D.
interactionMechanism
Indicates the process or means by which one entity affects, influences, or interacts with another.
-
E.
effectOnMachines
Indicates the influence or impact that one entity, condition, or action has on machines and their behavior or performance.
- 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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f794f649648190a79d90e6e67fe2dc |
completed | May 3, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.