Triple
T18591446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICL 1900 series |
E454376
|
entity |
| Predicate | hardwareTechnology |
P1482
|
FINISHED |
| Object | discrete transistor logic |
—
|
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: discrete transistor logic | Statement: [ICL 1900 series, hardwareTechnology, discrete transistor logic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hardwareTechnology Context triple: [ICL 1900 series, hardwareTechnology, discrete transistor logic]
-
A.
technologyNode
Indicates a relationship where an entity is associated with, implemented in, or characterized by a specific technology node or process technology level.
-
B.
hardwareComponent
Indicates that one entity is a physical hardware part or module that is contained in, attached to, or functionally part of another hardware system or device.
-
C.
hardwareCategory
Indicates that an item belongs to or is classified under a specific hardware category or type.
-
D.
hardwareUsed
Indicates that a particular piece of hardware is utilized or employed in performing an action, process, or function involving another entity.
-
E.
technologyType
chosen
Indicates the specific kind or category of technology associated with an entity or relationship.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e545b5bc688190bdfe3911ac6b2d76 |
completed | April 19, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.