Triple
T29390349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | microSD |
E745353
|
entity |
| Predicate | supportsLowVoltageMode |
P204199
|
FINISHED |
| Object | 1.8 V (UHS modes) |
—
|
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: 1.8 V (UHS modes) | Statement: [microSD, supportsLowVoltageMode, 1.8 V (UHS modes)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLowVoltageMode Context triple: [microSD, supportsLowVoltageMode, 1.8 V (UHS modes)]
-
A.
hasLowPowerVariant
Indicates that an entity has a related version or configuration designed to operate with reduced power consumption compared to the standard one.
-
B.
hasLowerPowerConsumptionThan
Indicates that one entity uses less power or energy than another entity under comparable conditions.
-
C.
supportsAutoLowLatencyMode
Indicates that the subject is capable of automatically enabling and managing a low-latency mode for its operations or interactions.
-
D.
supportsMaximumVoltage
Indicates that an entity is capable of safely operating at or up to a specified maximum voltage level.
-
E.
storesMultipleVoltageLevels
Indicates that an entity is capable of holding or maintaining more than one distinct voltage level simultaneously or over time.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a0346b487088190814e4bd0765cb609 |
completed | May 12, 2026, 3:26 p.m. |
| PD | Predicate disambiguation | batch_6a0346428c60819090e5ea815c0921ca |
completed | May 12, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_6a0346b3b2708190b713ce3dfee1734a |
completed | May 12, 2026, 3:26 p.m. |
Created at: April 28, 2026, 2:41 p.m.