Triple
T37460732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kel'Thuzad (card) |
E930909
|
entity |
| Predicate | releaseAdventure |
P193808
|
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: [Kel'Thuzad (card), releaseAdventure, Curse of Naxxramas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseAdventure Context triple: [Kel'Thuzad (card), releaseAdventure, Curse of Naxxramas]
-
A.
hasAdventureOn
Indicates that an entity participates in or experiences an adventure that takes place on or during a specified context, such as a time, location, or medium.
-
B.
releaseType
Indicates the kind or category of a release event or version associated with an entity.
-
C.
hasAdventureAt
Indicates that an entity experiences, undertakes, or is involved in an adventure at a specified location or setting.
-
D.
hasAdventurePlot
Indicates that a work’s storyline centers on an adventure, typically involving exciting, risky, or exploratory events and journeys.
-
E.
expansionAdventureType
Indicates the type or category of adventure associated with a particular expansion.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
| PDg | Predicate description generation | batch_69fd553c01488190b9fda48b4a728f04 |
completed | May 8, 2026, 3:15 a.m. |
Created at: May 3, 2026, 4:17 p.m.