Triple
T32541665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redstone 1 |
E831728
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Windows 10 development codename |
C23342
|
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: Windows 10 development codename Context triple: [Redstone 1, instanceOf, Windows 10 development codename]
-
A.
Microsoft Windows development codename
A Microsoft Windows development codename is a temporary, often thematic internal name used by Microsoft to identify and reference a specific in-development version or release of the Windows operating system before its official product name is announced.
-
B.
Microsoft Windows codename
chosen
A Microsoft Windows codename is an internal, often thematic or project-based name used by Microsoft to identify and refer to a specific Windows version or development cycle before its official release name is finalized.
-
C.
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.
-
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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:02 a.m.