Triple
T37462620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalimos, Primal Lord |
E930955
|
entity |
| Predicate | designedForDeckType |
P4066
|
FINISHED |
| Object | Elemental Shaman |
—
|
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: Elemental Shaman | Statement: [Kalimos, Primal Lord, designedForDeckType, Elemental Shaman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForDeckType Context triple: [Kalimos, Primal Lord, designedForDeckType, Elemental Shaman]
-
A.
hasDeckType
chosen
Indicates that an entity possesses or is associated with a specific type or category of deck.
-
B.
hasMultipleDecks
Indicates that an entity possesses more than one deck or layered level within its structure.
-
C.
upperDeckUsedFor
Indicates that the upper deck of an object or structure is utilized for a specified purpose or activity.
-
D.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
E.
cardSetType
Indicates the classification relationship that specifies what type or category a given card set belongs to.
- 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_69ff76ac40988190a34d858b5472ee2b |
completed | May 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69ff760a90948190a12fcb80e6e3e14b |
completed | May 9, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:17 p.m.