Triple
T37550548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multiplayer Havoc Pack |
E933580
|
entity |
| Predicate | developerOfBaseGame |
P187231
|
FINISHED |
| Object | High Moon Studios |
—
|
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: High Moon Studios | Statement: [Multiplayer Havoc Pack, developerOfBaseGame, High Moon Studios]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developerOfBaseGame Context triple: [Multiplayer Havoc Pack, developerOfBaseGame, High Moon Studios]
-
A.
developerOfContainingGame
Indicates that an entity is the developer responsible for creating the game that contains the referenced element or component.
-
B.
gameDeveloper
Indicates that one entity creates, designs, or develops the other entity, which is a game.
-
C.
gameDeveloperOwner
Indicates that one entity is the owner or primary controlling developer of a particular game.
-
D.
gameDeveloperOfOrigin
Indicates that an entity is the original creator or primary developing studio responsible for a particular game.
-
E.
expansionDeveloper
chosen
Indicates that an entity is responsible for creating, extending, or enhancing the expansion of another entity (such as a product, system, or project).
- 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_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: May 3, 2026, 4:17 p.m.