Triple
T37763523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imprisoned Demons |
E941347
|
entity |
| Predicate | rarityPattern |
P189201
|
FINISHED |
| Object | appear at multiple rarities across sets |
—
|
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: appear at multiple rarities across sets | Statement: [Imprisoned Demons, rarityPattern, appear at multiple rarities across sets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rarityPattern Context triple: [Imprisoned Demons, rarityPattern, appear at multiple rarities across sets]
-
A.
rarity
Indicates how uncommon or infrequently an entity or event occurs relative to others in a given context.
-
B.
craftingRarity
Indicates the rarity level associated with crafting an item or outcome within a system.
-
C.
rarityReason
Indicates the underlying cause or justification for why something is considered rare.
-
D.
cardRarityColor
Indicates the association between a card’s rarity level and the color used to represent that rarity.
-
E.
includesRarities
Indicates that one entity contains or encompasses specific rare or uncommon items, features, or elements associated with another entity.
- 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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbb9e69b7481909beaf8264d87c5e5 |
completed | May 6, 2026, 10 p.m. |
Created at: May 3, 2026, 4:19 p.m.