Triple
T25616906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duron |
E642182
|
entity |
| Predicate | coreVoltage |
P158914
|
FINISHED |
| Object | varies by stepping and model |
—
|
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: varies by stepping and model | Statement: [Duron, coreVoltage, varies by stepping and model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreVoltage Context triple: [Duron, coreVoltage, varies by stepping and model]
-
A.
supplyVoltageRange
Indicates the range of electrical supply voltages within which the entity is designed or allowed to operate.
-
B.
typicalSupplyVoltage
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.
typicalSupplyVoltageRange
Indicates the usual minimum-to-maximum voltage range within which a device or component is designed to be normally powered and operate correctly.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5f9e8734c8190a214685b1647abe1 |
completed | May 2, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 5 p.m.