Triple
T37464135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myra's Unstable Element |
E930991
|
entity |
| Predicate | designerContext |
P115298
|
FINISHED |
| Object | Supports combo-oriented Rogue decks |
—
|
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: Supports combo-oriented Rogue decks | Statement: [Myra's Unstable Element, designerContext, Supports combo-oriented Rogue decks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designerContext Context triple: [Myra's Unstable Element, designerContext, Supports combo-oriented Rogue decks]
-
A.
hasDesignContext
chosen
Indicates that something is associated with, or defined within, a particular design context or design environment.
-
B.
designerType
Indicates the specific kind or category of designer role associated with an entity.
-
C.
designScope
Indicates the range, boundaries, or extent of responsibility covered by a particular design activity or decision.
-
D.
designerAlias
Indicates that one name or label is used as an alternative alias for a designer.
-
E.
creatorContext
Indicates the situational or environmental context in which a creator produced or is associated with a work or entity.
- 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_69ff779e3f0c8190a861f1e4000fd9d9 |
completed | May 9, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69ff77202638819086e4b9f9c0bc7b31 |
completed | May 9, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:17 p.m.