Triple
T38644039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mag'har Orcs |
E938671
|
entity |
| Predicate | introducedAsPlayableIn |
P192473
|
FINISHED |
| Object | World of Warcraft: Battle for Azeroth |
—
|
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: Battle for Azeroth | Statement: [Mag'har Orcs, introducedAsPlayableIn, World of Warcraft: Battle for Azeroth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsPlayableIn Context triple: [Mag'har Orcs, introducedAsPlayableIn, World of Warcraft: Battle for Azeroth]
-
A.
playInGameIntroduced
Indicates that an entity participates as a playable element within the specific game in which it was first introduced.
-
B.
introducedInGameAs
Indicates that an entity first appeared or was made available within a specific game title.
-
C.
playableContentIntroducedIn
chosen
Indicates that a piece of playable content was first introduced or made available in a specific release, version, or installment.
-
D.
introducedToGame
Indicates that one entity caused or facilitated another entity’s initial exposure or introduction to a particular game.
-
E.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff46afe7e481908f2862ed11c88db2 |
completed | May 9, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69ff45e9151881909c444a655e852165 |
completed | May 9, 2026, 2:34 p.m. |
Created at: May 3, 2026, 4:32 p.m.