Triple
T37461909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Year of the Kraken |
E930938
|
entity |
| Predicate | appliesToGameMode |
P119199
|
FINISHED |
| Object | Hearthstone Standard format |
—
|
NE NERFINISHED |
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: Hearthstone Standard format | Statement: [Year of the Kraken, appliesToGameMode, Hearthstone Standard format]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToGameMode Context triple: [Year of the Kraken, appliesToGameMode, Hearthstone Standard format]
-
A.
appearsInGameMode
Indicates that an entity is present, available, or featured within a specified game mode.
-
B.
availableInMode
chosen
Indicates that something can be used, accessed, or functions within a specified mode or operational setting.
-
C.
appliesToFeature
Indicates that something (such as a rule, constraint, or configuration) is relevant to, or governs, a specific feature.
-
D.
primaryGameMode
Indicates the main or default game mode associated with a particular game or gaming context.
-
E.
gameModeRelevance
Indicates how strongly or in what way something is related or applicable to a particular game mode.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffb1218cb08190a814c7f0833501a7 |
completed | May 9, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69ffb083d6988190b2757e0cfd629b75 |
completed | May 9, 2026, 10:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.