Triple
T37457102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freeze Mage |
E930826
|
entity |
| Predicate | typicalGameplan |
P70722
|
FINISHED |
| Object | control early and mid game with spells |
—
|
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: control early and mid game with spells | Statement: [Freeze Mage, typicalGameplan, control early and mid game with spells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGameplan Context triple: [Freeze Mage, typicalGameplan, control early and mid game with spells]
-
A.
typicalGame
Indicates a relationship where one entity is characterized as a standard, representative, or commonly occurring example of a game for the other entity or context.
-
B.
postGamesPlan
Indicates that an entity publishes or shares a plan or strategy related to games after they have concluded.
-
C.
planning
Indicates that an entity is engaged in organizing or devising a future action, event, or course of behavior involving another entity or entities.
-
D.
hasTypicalPlan
chosen
Indicates that there is a standard or commonly followed plan, procedure, or course of action typically associated with the given entity or situation.
-
E.
planningChallenge
Indicates a situation where creating, organizing, or coordinating a plan is difficult or problematic for the involved entities.
- 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_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.