Triple
T29416963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BioWare Austin |
E746050
|
entity |
| Predicate | hasGameTypeSpecialization |
P10208
|
FINISHED |
| Object | MMO live operations |
—
|
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: MMO live operations | Statement: [BioWare Austin, hasGameTypeSpecialization, MMO live operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGameTypeSpecialization Context triple: [BioWare Austin, hasGameTypeSpecialization, MMO live operations]
-
A.
hasGameType
Indicates that an entity (such as a game or match) is associated with a specific category or type of game.
-
B.
includesGameType
chosen
Indicates that one entity contains or supports a particular type or category of game.
-
C.
hasSpecialGames
Indicates that an entity is associated with particular games that are distinguished from its regular or standard games in some special way.
-
D.
hasPlayType
Indicates the type or category of play associated with an event, action, or performance.
-
E.
hasCardGameVariant
Indicates that one game is a variation or modified form of another card 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 3:02 p.m.