Triple
T29181776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TI OMAP3430 |
E739762
|
entity |
| Predicate | hasMemoryController |
P114055
|
FINISHED |
| Object | LPDDR |
—
|
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: LPDDR | Statement: [TI OMAP3430, hasMemoryController, LPDDR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemoryController Context triple: [TI OMAP3430, hasMemoryController, LPDDR]
-
A.
integratedMemoryController
Indicates that a memory controller is built directly into another component (such as a processor or chipset) rather than existing as a separate, external unit.
-
B.
memoryController
chosen
Indicates a relationship where one entity manages, coordinates, or regulates access to memory resources for another entity or system.
-
C.
supportsMemoryBusWidth
Indicates that one entity is compatible with or able to operate using the specified memory bus width of another entity.
-
D.
supportsECCMemory
Indicates that one entity provides compatibility with or the capability to use ECC (Error-Correcting Code) memory in relation to another entity.
-
E.
hasRAM
Indicates that an entity possesses or is equipped with a specified amount or type of random-access memory (RAM).
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 28, 2026, 11:57 a.m.