Triple
T25533950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ring Transformer |
E639994
|
entity |
| Predicate | voltageOutput |
P120434
|
FINISHED |
| Object | 12V low-voltage output |
—
|
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: 12V low-voltage output | Statement: [Ring Transformer, voltageOutput, 12V low-voltage output]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voltageOutput Context triple: [Ring Transformer, voltageOutput, 12V low-voltage output]
-
A.
typicalElectricalOutputRange
Indicates the usual range of electrical power or energy output that an entity is expected to produce under normal operating conditions.
-
B.
typicalSupplyVoltage
chosen
Indicates the standard or commonly used voltage level at which a device or component is normally supplied or operated.
-
C.
typicalVoltageRange
Indicates the usual minimum-to-maximum voltage interval within which something is designed or expected to operate.
-
D.
supplyVoltageType
Indicates the type or category of supply voltage associated with or required by an entity.
-
E.
signalVoltage
Indicates the electrical potential level carried by a signal in a circuit or communication channel.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8652c908190bee57d3f2663e6b2 |
completed | May 2, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 3:16 p.m.