Triple
T31583293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DEC Alpha |
E805880
|
entity |
| Predicate | firstImplementation |
—
|
GENERATED |
| Object | DECchip 21064 |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstImplementation Context triple: [DEC Alpha, firstImplementation, DECchip 21064]
-
A.
firstImplementedBy
chosen
Indicates that the subject was initially realized, executed, or put into practice by the specified agent or entity.
-
B.
firstRelease
Indicates that one entity is the initial or earliest release (in time or sequence) of another entity, such as a product, work, or version.
-
C.
firstDeveloperRelease
Indicates the date or version when a developer-focused or pre-release version of a product was first made available.
-
D.
firstPerformedWith
Indicates that an action or work was initially performed in conjunction with a specified collaborator, group, or medium.
-
E.
firstDemonstrated
Indicates that one entity was the earliest to show, prove, or exemplify a particular concept, method, or capability in relation to another entity or context.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:24 p.m.