Triple
T38110494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stormwind Harbor |
E951641
|
entity |
| Predicate | inGameWorld |
P190569
|
FINISHED |
| Object | 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: Azeroth | Statement: [Stormwind Harbor, inGameWorld, Azeroth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inGameWorld Context triple: [Stormwind Harbor, inGameWorld, Azeroth]
-
A.
inGameZone
Indicates that an entity is located within a defined game zone or area of the game world.
-
B.
inGameType
Indicates that an entity participates in or belongs to a specific type or category within a game (e.g., game mode, classification, or role).
-
C.
inGameName
Indicates that one entity is the name used by another entity within a specific game context.
-
D.
inGamePerspective
Indicates that something is being viewed, described, or experienced from within the context and point of view of the game world itself.
-
E.
homeGameWorld
Indicates that a game or match is being played in the home world or home venue associated with a particular team or participant.
- 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_69f76f065ed08190bdfb1b6d817f5b39 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fccbd6b7688190b746803cf78d5704 |
completed | May 7, 2026, 5:28 p.m. |
Created at: May 3, 2026, 4:21 p.m.