Triple
T2979753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advanced Micro Devices |
E80480
|
entity |
| Predicate | R&DFocus |
P31
|
FINISHED |
| Object | high-performance computing |
—
|
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: high-performance computing | Statement: [Advanced Micro Devices, R&DFocus, high-performance computing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: R&DFocus Context triple: [Advanced Micro Devices, R&DFocus, high-performance computing]
-
A.
formerFocus
Indicates that an entity previously served as the primary focus or main subject of attention, but no longer holds that status.
-
B.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
C.
laterLensType
Indicates that one lens type occurs or is used at a later time than another lens type in a temporal sequence.
-
D.
focusType
Indicates the specific kind or category of focus or attention that is being applied to or associated with an entity or interaction.
-
E.
focusesBy
Indicates that one entity directs its attention, effort, or emphasis toward another entity or specific aspect of it.
- 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad999cca40819082e2d6d10bdb7872 |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad9611fc348190a5d17d237f653f60 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.