Triple
T30178431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeForce 20 Series |
E767127
|
entity |
| Predicate | usesProcessTechnology |
P76106
|
FINISHED |
| Object | 12 nm FinFET (TSMC) |
—
|
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: 12 nm FinFET (TSMC) | Statement: [GeForce 20 Series, usesProcessTechnology, 12 nm FinFET (TSMC)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesProcessTechnology Context triple: [GeForce 20 Series, usesProcessTechnology, 12 nm FinFET (TSMC)]
-
A.
appliesTechnologyIn
Indicates that an entity makes use of or implements a particular technology within a specific context or activity.
-
B.
mainGenerationTechnology
Indicates the primary technology or method used to generate something, typically identifying the dominant production or generation approach among possible alternatives.
-
C.
usesVehicleTechnology
Indicates that an entity employs or applies a specific vehicle-related technology in its operations, products, or activities.
-
D.
fabricationTechnology
chosen
Indicates the manufacturing or production method used to create or realize an entity.
-
E.
laterUsedTechnology
Indicates that one entity adopted or employed a technology after another entity had already used 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_69f2247ba20c81909d34f2bfed706e1e |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 29, 2026, 7:25 p.m.