Triple
T35760323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CDC 6600 |
E1033552
|
entity |
| Predicate | usedTransistorType |
P64160
|
FINISHED |
| Object | silicon transistors |
—
|
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: silicon transistors | Statement: [CDC 6600, usedTransistorType, silicon transistors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedTransistorType Context triple: [CDC 6600, usedTransistorType, silicon transistors]
-
A.
transistorType
Indicates the specific kind or category of transistor associated with an entity (e.g., BJT, MOSFET, JFET).
-
B.
usedSemiconductorType
chosen
Indicates that one entity employs or incorporates a specific type of semiconductor in its design, construction, or operation.
-
C.
usesTransistorPolarity
Indicates that one entity employs or depends on a specific type or configuration of transistor polarity in relation to another entity or context.
-
D.
transistorCount
Indicates the number of transistors contained within an electronic component or device.
-
E.
transistorCountApprox
Indicates an approximate relationship specifying the estimated number of transistors associated with an entity.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.