Triple
T8507739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DRAM |
E201374
|
entity |
| Predicate | relativeCost |
P9543
|
FINISHED |
| Object | lower cost per bit than SRAM |
—
|
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 cost per bit than SRAM | Statement: [DRAM, relativeCost, lower cost per bit than SRAM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeCost Context triple: [DRAM, relativeCost, lower cost per bit than SRAM]
-
A.
relativePrice
chosen
Indicates a comparison of the cost or monetary value of one entity relative to another.
-
B.
reducedCostOf
Indicates that one entity represents a lowered or discounted cost associated with another entity, typically compared to a standard or original price.
-
C.
priceRelationship
Indicates a comparative relationship between the prices of two entities, such as one being higher, lower, or equal to the other.
-
D.
estimatedCost
Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
-
E.
costToUser
Indicates the amount of cost or expense that is borne by, charged to, or incurred by the user.
- 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_69ca8320e5748190ac2c585a0bba8193 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe5de18448190a695eec609b34e1a |
completed | March 31, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69cbd10cfd208190a519049fad32c508 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:14 p.m.