Triple
T37085676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsunami |
E918279
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Apple internal hardware codename |
C12165
|
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: Apple internal hardware codename Context triple: [Tsunami, instanceOf, Apple internal hardware codename]
-
A.
Apple project codename
chosen
An Apple project codename is a temporary, often thematic internal name used by Apple to identify and reference a product or initiative during its confidential development phase before the official public name is announced.
-
B.
computer codename
A computer codename is a unique, often thematic or symbolic label used internally to identify a specific hardware or software project, version, or configuration before its official public name is assigned.
-
C.
Intel codename
An Intel codename is an internal, often thematic or location-based name used by Intel to identify and reference a specific processor, platform, or technology project before and sometimes alongside its official product branding.
-
D.
Microsoft internal codename
A Microsoft internal codename is a temporary, often non-descriptive name used within the company to refer to a product, feature, or project before its official public name is finalized and announced.
-
E.
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.
- 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_69f76e9952b88190a6fe01ba01476520 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.