Triple
T17517535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raspberry Pi Pico |
E426603
|
entity |
| Predicate | coreVoltageV |
P120434
|
FINISHED |
| Object | 3.3 |
—
|
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: 3.3 | Statement: [Raspberry Pi Pico, coreVoltageV, 3.3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreVoltageV Context triple: [Raspberry Pi Pico, coreVoltageV, 3.3]
-
A.
supplyVoltageRange
Indicates the range of electrical supply voltages within which the entity is designed or allowed to operate.
-
B.
typicalSupplyVoltage
chosen
Indicates the standard or commonly used voltage level at which a device or component is normally supplied or operated.
-
C.
supplyVoltageType
Indicates the type or category of supply voltage associated with or required by an entity.
-
D.
typicalVoltagePerCell
Indicates the standard or commonly expected voltage value associated with each individual cell in a multi-cell system or device.
-
E.
CPUCoreConfiguration
Indicates the specific arrangement and characteristics of processor cores allocated or defined within a computing system.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452615a8481909974e9855ea7a8e4 |
completed | April 19, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.