Triple
T37540496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valeera Sanguinar |
E933312
|
entity |
| Predicate | cardClassIn |
P99617
|
FINISHED |
| Object | Rogue in Hearthstone |
—
|
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: Rogue in Hearthstone | Statement: [Valeera Sanguinar, cardClassIn, Rogue in Hearthstone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cardClassIn Context triple: [Valeera Sanguinar, cardClassIn, Rogue in Hearthstone]
-
A.
cardClass
chosen
Indicates the classification or category to which a given card belongs within a defined card system or schema.
-
B.
cardType
Indicates the classification or category assigned to a card within a given system or context.
-
C.
cardFormat
Indicates the specific layout or structural style in which a card or card-like item is presented or encoded.
-
D.
cardExample
Indicates that something is an illustrative or sample instance of a card (such as a prototype, demo, or example card) rather than a primary or production card.
-
E.
cardVariant
Indicates that one card is a specific version or variation of another base card.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:17 p.m.