Triple
T36965177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Team Silent |
E914409
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Konami development division |
C29391
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Konami development division Context triple: [Team Silent, instanceOf, Konami development division]
-
A.
Capcom franchise
A Capcom franchise is a series of related video games and associated media developed or published by Capcom, typically sharing common characters, settings, and gameplay themes.
-
B.
Sony division
A Sony division is an organizational unit within Sony Corporation responsible for a specific business area, product line, or regional market, operating with its own management, strategy, and performance goals.
-
C.
Sega internal development team
A Sega internal development team is an in-house group of designers, programmers, artists, and producers responsible for creating, iterating on, and maintaining Sega’s video game titles and related software projects.
-
D.
video game company branch
chosen
A video game company branch is a regional or specialized division of a larger game development or publishing organization, responsible for localized operations such as development, marketing, distribution, or support within a specific geographic area or market segment.
-
E.
Sony Group subsidiary
A Sony Group subsidiary is a company that is majority-owned or otherwise controlled by Sony Group Corporation, operating under its corporate umbrella while focusing on specific business areas such as electronics, entertainment, or financial services.
- F. None of above.
Provenance (1 batch)
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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.