Triple
T37458090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murloc |
E930848
|
entity |
| Predicate | mechanicalThemeInHearthstone |
P188661
|
FINISHED |
| Object | Swarming the board |
—
|
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: Swarming the board | Statement: [Murloc, mechanicalThemeInHearthstone, Swarming the board]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mechanicalThemeInHearthstone Context triple: [Murloc, mechanicalThemeInHearthstone, Swarming the board]
-
A.
keyMechanic
Indicates that the referenced element functions as a central or essential gameplay mechanic within a system or experience.
-
B.
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.
-
C.
similarToMechanic
Indicates that one entity resembles or shares key characteristics with a mechanic in function, role, or behavior.
-
D.
deckArchetype
Indicates a classification relationship where a specific deck is associated with a particular strategic archetype or style of play.
-
E.
mechanicalFunction
Indicates that one entity serves as the mechanical role, operation, or function performed by another entity or system.
- F. None of above. chosen
Provenance (4 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_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbacaea12c8190a4c99e64335f0e7e |
completed | May 6, 2026, 9:03 p.m. |
Created at: May 3, 2026, 4:17 p.m.