Triple
T31776361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLC (multi-level cell) |
E811073
|
entity |
| Predicate | typicalProgramEraseCycles |
P97058
|
FINISHED |
| Object | lower than SLC |
—
|
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: lower than SLC | Statement: [MLC (multi-level cell), typicalProgramEraseCycles, lower than SLC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalProgramEraseCycles Context triple: [MLC (multi-level cell), typicalProgramEraseCycles, lower than SLC]
-
A.
typicalNumberOfCycles
chosen
Indicates the usual or characteristic count of cycles associated with an entity, process, or event.
-
B.
catalogueNumberOfCycle
Indicates that an entity is assigned a specific catalogue number identifying a particular cycle within a cataloging system.
-
C.
numberOfStrokesPerCycle
Indicates the count of individual strokes that occur during one complete cycle of a repeated action or process.
-
D.
capacityPerCycle
Indicates the amount of output or throughput that can be achieved during a single operational cycle of a process or system.
-
E.
supportsWearLeveling
Indicates that one entity provides functionality or mechanisms to perform wear leveling for another entity or resource.
- 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_69f348e544a48190ab6e700b05f6438c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:35 p.m.