Triple
T31776297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLC (single-level cell) |
E811072
|
entity |
| Predicate | hasCostPerBit |
P73251
|
FINISHED |
| Object | high |
—
|
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 | Statement: [SLC (single-level cell), hasCostPerBit, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCostPerBit Context triple: [SLC (single-level cell), hasCostPerBit, high]
-
A.
hasLowerCostPerBitThan
Indicates that the cost required to transmit or store each unit of data (bit) for one entity is lower than that for another entity.
-
B.
hasCost
chosen
Indicates that one entity requires a specified amount of resources (such as money, time, or effort) to be obtained, used, or maintained by another entity.
-
C.
hasBasicRateBitrate
Indicates that an entity is associated with a fundamental or default data transmission bitrate value.
-
D.
feeUnit
Indicates the unit of measurement or currency in which a fee amount is expressed.
-
E.
usesBillingModel
Indicates that one entity applies or operates under a particular billing model for charging or pricing purposes.
- 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_6a03173dd4988190a38175b63cba9f09 |
completed | May 12, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_6a031700ade88190afd217d5966b03b4 |
completed | May 12, 2026, 12:03 p.m. |
Created at: April 30, 2026, 11:35 p.m.