Triple
T26006971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Socket AM2 |
E646785
|
entity |
| Predicate | supportedMemoryVoltage |
P193402
|
FINISHED |
| Object | 1.8 V DDR2 |
—
|
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 DDR2 | Statement: [Socket AM2, supportedMemoryVoltage, 1.8 V DDR2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedMemoryVoltage Context triple: [Socket AM2, supportedMemoryVoltage, 1.8 V DDR2]
-
A.
coreVoltage
Indicates the electrical potential difference supplied to the core component of a device or system.
-
B.
supportsLPDDR4Memory
Indicates that an entity is compatible with and can operate using LPDDR4 memory technology.
-
C.
supportsLPDDR4XMemory
Indicates that an entity is compatible with and can operate using LPDDR4X memory modules.
-
D.
memoryConfigurations
Indicates how memory resources are arranged, allocated, or structured within a system or component.
-
E.
supportsMemoryBusWidth
Indicates that one entity is compatible with or able to operate using the specified memory bus width of another entity.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
| PDg | Predicate description generation | batch_69fd474a71648190b6b6ae4991db81b1 |
completed | May 8, 2026, 2:15 a.m. |
Created at: April 22, 2026, 9:01 a.m.