Triple
T35760132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CDC 6600 |
E1033548
|
entity |
| Predicate | numberOfPeripheralProcessors |
P206039
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [CDC 6600, numberOfPeripheralProcessors, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfPeripheralProcessors Context triple: [CDC 6600, numberOfPeripheralProcessors, 10]
-
A.
usedPeripheralProcessorsFor
Indicates that an entity made use of peripheral processing units or devices to perform or support its operations or tasks.
-
B.
maxNumberOfProcessors
Indicates the maximum number of processors that are allowed or supported in a given context or configuration.
-
C.
supportsProcessorCoreCount
Indicates that one entity is compatible with or able to operate using a specified number of processor cores in another entity.
-
D.
hasProcessingUnits
Indicates that an entity is equipped with or contains one or more processing units (such as CPUs, GPUs, or similar computational components).
-
E.
smallCoreCount
Indicates that an entity has a relatively low number of processing cores compared to typical or expected configurations.
- F. None of above. chosen
Provenance (4 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_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037ce53de881908cf14141cf3bc570 |
completed | May 12, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:06 p.m.