Triple
T25991705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMD 486 |
E646369
|
entity |
| Predicate | technologyNodeRange |
P28420
|
FINISHED |
| Object | 0.8 µm to 0.35 µm (depending on model) |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 0.8 µm to 0.35 µm (depending on model) | Statement: [AMD 486, technologyNodeRange, 0.8 µm to 0.35 µm (depending on model)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyNodeRange Context triple: [AMD 486, technologyNodeRange, 0.8 µm to 0.35 µm (depending on model)]
-
A.
technologyNode
chosen
Indicates a relationship where an entity is associated with, implemented in, or characterized by a specific technology node or process technology level.
-
B.
targetTDPRange
Indicates the specified thermal design power (TDP) range that a component or system is intended or required to operate within.
-
C.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
-
D.
technologyLevel
Indicates the degree of technological advancement or sophistication associated with an entity relative to others or to a defined scale.
-
E.
technologyClass
Indicates the classification or category of technology to which an entity belongs.
- F. None of above.
Provenance (3 batches)
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_69e77e88cb8481908da31d4a00661f55 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605484f2081908bc76568678ffe68 |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 8:57 a.m.