Triple
T37592243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loatheb |
E935287
|
entity |
| Predicate | HearthstoneSet |
P187881
|
FINISHED |
| Object | Curse of Naxxramas |
—
|
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: Curse of Naxxramas | Statement: [Loatheb, HearthstoneSet, Curse of Naxxramas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HearthstoneSet Context triple: [Loatheb, HearthstoneSet, Curse of Naxxramas]
-
A.
yearOfHearthstone
Indicates the specific year in which a given Hearthstone-related event, release, or context took place.
-
B.
cardSet
chosen
Indicates that an item belongs to, or is grouped within, a particular set or collection of cards.
-
C.
hasExpansionSetNumber
Indicates that an entity is associated with a specific numbered position or identifier within an expansion set.
-
D.
plannedMTG-ICount
Indicates that there is a recorded count of planned meetings associated with the given entities.
-
E.
iconicTCGCard
Indicates that a trading card game (TCG) card is widely recognized as emblematic or highly representative of its game or format.
- 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.