Triple
T31776348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLC (multi-level cell) |
E811073
|
entity |
| Predicate | storesMultipleVoltageLevels |
P172289
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [MLC (multi-level cell), storesMultipleVoltageLevels, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storesMultipleVoltageLevels Context triple: [MLC (multi-level cell), storesMultipleVoltageLevels, true]
-
A.
supportsMultipleBatteryCapacities
Indicates that something is designed to work with or accommodate more than one distinct battery capacity option.
-
B.
typicalVoltageRange
Indicates the usual minimum-to-maximum voltage interval within which something is designed or expected to operate.
-
C.
supplyVoltageType
Indicates the type or category of supply voltage associated with or required by an entity.
-
D.
usesElectricityVoltage
Indicates that one entity operates using or is characterized by a specified level of electrical voltage supplied by another entity or source.
-
E.
typicalSupplyVoltage
Indicates the standard or commonly used voltage level at which a device or component is normally supplied or operated.
- 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_69f348e544a48190ab6e700b05f6438c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa21f2508190a204a424ffc00ca6 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aac95c1481909fff33702d0a6c37 |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 30, 2026, 11:35 p.m.