Triple
T28897677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midway |
E732870
|
entity |
| Predicate | gameDesignStyle |
P137584
|
FINISHED |
| Object | fast-paced arcade gameplay |
—
|
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: fast-paced arcade gameplay | Statement: [Midway, gameDesignStyle, fast-paced arcade gameplay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameDesignStyle Context triple: [Midway, gameDesignStyle, fast-paced arcade gameplay]
-
A.
gameDesignSpecialty
Indicates that one entity has a particular area of specialization or focus within the field of game design in relation to another entity.
-
B.
gameModeDesign
Indicates that one entity defines or specifies the rules, structure, or configuration of a particular game mode for another entity.
-
C.
designedGame
Indicates that one entity is the creator or designer responsible for the conception and development of a particular game.
-
D.
productionDesignStyle
Indicates the visual and aesthetic approach used in designing the overall look and environment of a production.
-
E.
coreDesignStyle
chosen
Indicates the primary or defining design style that characterizes an entity’s overall aesthetic or structural approach.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 8 a.m.