Triple
T31486571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TSMC 4N |
E803291
|
entity |
| Predicate | technologyNodeClass |
P28420
|
FINISHED |
| Object | 5 nm-class |
—
|
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: 5 nm-class | Statement: [TSMC 4N, technologyNodeClass, 5 nm-class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyNodeClass Context triple: [TSMC 4N, technologyNodeClass, 5 nm-class]
-
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.
technologyClass
Indicates the classification or category of technology to which an entity belongs.
-
C.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
-
D.
technologyCounterpartOf
Indicates a relationship where one technology serves as an equivalent, alternative, or corresponding counterpart to another technology.
-
E.
technologyAgnostic
Indicates that something is designed or functions independently of any specific technology, platform, or vendor, and can work with multiple technological options.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 9:35 p.m.