Triple
T37461919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Year of the Kraken |
E930938
|
entity |
| Predicate | rotationRemovedFromStandard |
P187931
|
FINISHED |
| Object | Curse of Naxxramas |
—
|
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: Curse of Naxxramas | Statement: [Year of the Kraken, rotationRemovedFromStandard, Curse of Naxxramas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rotationRemovedFromStandard Context triple: [Year of the Kraken, rotationRemovedFromStandard, Curse of Naxxramas]
-
A.
rotationSetOutOfStandard
chosen
Indicates that a rotation or schedule has been configured in a way that deviates from the defined standard settings or norms.
-
B.
rotationProcess
Indicates a process in which something is turned or rotated around an axis or point over time.
-
C.
rotationType
Indicates the specific kind or mode of rotational movement or orientation applied in a given context.
-
D.
brokeIntoRotation
Indicates that an entity newly entered into an established rotation or regular sequence of participation or usage.
-
E.
rotationAction
Indicates an action where an entity is turned or rotated around a point, axis, or center by a specified amount or orientation.
- 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_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.