Triple
T37553817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magmadar |
E933646
|
entity |
| Predicate | isInGameMode |
P69305
|
FINISHED |
| Object | World of Warcraft Classic |
—
|
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: World of Warcraft Classic | Statement: [Magmadar, isInGameMode, World of Warcraft Classic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInGameMode Context triple: [Magmadar, isInGameMode, World of Warcraft Classic]
-
A.
appearsInGameMode
chosen
Indicates that an entity is present, available, or featured within a specified game mode.
-
B.
gameModeStatus
Indicates the current state or condition of a game mode, such as whether it is active, available, or in a particular operational phase.
-
C.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
-
D.
isGameSavingPlay
Indicates that a particular play or action prevents an imminent loss or major setback, effectively preserving a win or favorable outcome in a game or competition.
-
E.
hasInGameCategory
Indicates that an in-game item, action, or entity belongs to a specific predefined category within the game’s classification system.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.