Triple
T37460786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spectral Knight |
E930910
|
entity |
| Predicate | adventure |
P187919
|
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: [Spectral Knight, adventure, Curse of Naxxramas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adventure Context triple: [Spectral Knight, adventure, Curse of Naxxramas]
-
A.
hasPerilousAdventure
Indicates that an entity experiences, undertakes, or is involved in a dangerous or high-risk adventure.
-
B.
adventureWing
chosen
Indicates that one entity is associated with, located in, or part of an "adventure wing" area or section, typically designated for adventurous or exploratory activities.
-
C.
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.
-
D.
hasAdventureAt
Indicates that an entity experiences, undertakes, or is involved in an adventure at a specified location or setting.
-
E.
settingOfAdventure
Indicates that a location or environment serves as the primary setting where an adventure takes place.
- 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_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.