Triple

T37515796
Position Surface form Disambiguated ID Type / Status
Subject Runic Games E932629 entity
Predicate employeeBackground P130749 FINISHED
Object former Blizzard North staff LITERAL FINISHED

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: former Blizzard North staff | Statement: [Runic Games, employeeBackground, former Blizzard North staff]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: employeeBackground
Context triple: [Runic Games, employeeBackground, former Blizzard North staff]
  • A. candidateBackground
    Indicates that there is information or context describing a candidate’s prior experience, qualifications, or history.
  • B. requiredBackgroundCheck
    Indicates that an entity must undergo or has undergone a mandatory background check as a condition for participation, access, or approval in relation to another entity.
  • C. employmentCharacteristic
    Indicates a specific attribute, condition, or quality associated with a person’s employment or job situation.
  • D. employedAfter
    Indicates that one entity became employed by another entity at a point in time later than a referenced employment event or period.
  • E. economicRolePast chosen
    Indicates that an entity previously held a specific economic function, position, or role in the past.
  • 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_69f76ec730988190b5aa4f9cb9afd518 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fd0b92f42881908cd77e3f058adcc2 completed May 7, 2026, 10 p.m.
PD Predicate disambiguation batch_69fd0a3d68d4819094d92040f7c48d7c completed May 7, 2026, 9:55 p.m.
Created at: May 3, 2026, 4:17 p.m.