Triple
T31776283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLC (single-level cell) |
E811072
|
entity |
| Predicate | hasWriteSpeed |
P14421
|
FINISHED |
| Object | high write speed |
—
|
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: high write speed | Statement: [SLC (single-level cell), hasWriteSpeed, high write speed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWriteSpeed Context triple: [SLC (single-level cell), hasWriteSpeed, high write speed]
-
A.
writingSpeed
chosen
Indicates the rate at which an entity produces written content over a given period of time.
-
B.
readSpeed
Indicates the rate at which an entity reads or processes written material.
-
C.
hasClockSpeed
Indicates that an entity (typically a processor or device) operates at a specified clock frequency or speed.
-
D.
hasServiceSpeed
Indicates that an entity provides a service operating at a specified speed or performance rate.
-
E.
hasHigherThroughputThan
Indicates that one entity can process or transmit a greater volume of work, data, or operations per unit time than another entity.
- 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_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:35 p.m.