Triple
T20190817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nintendo EPD |
E492973
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | internal division of Nintendo |
C42906
|
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: internal division of Nintendo Context triple: [Nintendo EPD, instanceOf, internal division of Nintendo]
-
A.
Nintendo codename
A Nintendo codename is an internal, often secret project name used by Nintendo to refer to unreleased or in-development hardware, software, or services before their official titles are announced.
-
B.
Nintendo franchise element
A Nintendo franchise element is any recurring character, object, location, mechanic, or symbol that originates from and helps define one of Nintendo’s game series or intellectual properties.
-
C.
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.
-
D.
Nintendo network service
A Nintendo network service is an online platform provided by Nintendo that enables digital distribution, multiplayer connectivity, account management, and related online features for Nintendo gaming systems and software.
-
E.
Nintendo executive
A Nintendo executive is a high-level decision-maker responsible for guiding the company’s strategic direction, overseeing game and hardware portfolios, and managing business operations to sustain Nintendo’s brand and market success.
- F. None of above. chosen
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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:37 p.m.