Triple
T30404890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R-Car SoC |
E773451
|
entity |
| Predicate | typicalMemorySupport |
P9335
|
FINISHED |
| Object | DDR memory |
—
|
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: DDR memory | Statement: [R-Car SoC, typicalMemorySupport, DDR memory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMemorySupport Context triple: [R-Car SoC, typicalMemorySupport, DDR memory]
-
A.
typicalRAMRange
Indicates the usual or commonly expected range of RAM capacity associated with an entity.
-
B.
typicalRAMRangeMB
Indicates the usual or expected range of RAM capacity, measured in megabytes, associated with an entity.
-
C.
hasMemoryIn
Indicates that an entity possesses or stores memory, information, or experiences within a specified context, location, or medium.
-
D.
hasRAM
chosen
Indicates that an entity possesses or is equipped with a specified amount or type of random-access memory (RAM).
-
E.
builtInMemoryOf
Indicates that something was constructed as a tribute or commemoration to a particular person, group, or event.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:03 p.m.