Triple
T7980164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Core m3-8100Y |
E185550
|
entity |
| Predicate | l3CacheSize |
P80123
|
FINISHED |
| Object | 4 MB |
—
|
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: 4 MB | Statement: [Intel Core m3-8100Y, l3CacheSize, 4 MB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: l3CacheSize Context triple: [Intel Core m3-8100Y, l3CacheSize, 4 MB]
-
A.
l1CacheSize
Indicates the size or capacity of an entity’s level-1 (L1) cache memory.
-
B.
l2CacheSizeRange
Indicates the range of possible sizes for an entity’s level-2 (L2) cache.
-
C.
l1CachePerLittleCore
Indicates the size or capacity of the level-1 cache associated with each little (low-power) core in a processor.
-
D.
L2Cache
Indicates that one entity functions as a level-2 cache for another, storing intermediate data or results to speed up repeated access or computation.
-
E.
l2CacheBigCores
Indicates that the relationship or action involves the L2 cache associated with the system’s big (high-performance) cores.
- 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_69ca829851908190b4e03829353ee7c3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c261904819086910898071f3629 |
completed | March 31, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69cb048009a08190b4c577208a9f8f76 |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bbbacc81909c6cf8ec35314bbb |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:14 p.m.