Triple
T25616933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMD K6-2 |
E642183
|
entity |
| Predicate | L2CacheLocation |
P159161
|
FINISHED |
| Object | motherboard-based cache |
—
|
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: motherboard-based cache | Statement: [AMD K6-2, L2CacheLocation, motherboard-based cache]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: L2CacheLocation Context triple: [AMD K6-2, L2CacheLocation, motherboard-based cache]
-
A.
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.
-
B.
l2CacheType
Indicates the specific configuration or design category of an entity’s level-2 (L2) cache in a memory hierarchy.
-
C.
L2CacheAssociativity
Indicates how many distinct cache lines in the L2 cache can map to the same memory address set, defining the degree of parallel placement for data in that cache level.
-
D.
l2CacheShared
Indicates that two or more processing units share the same level-2 (L2) cache resource.
-
E.
l2CacheTypicalSize
Indicates the typical or standard size of an entity’s level-2 (L2) cache in a computing system.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5f9e8734c8190a214685b1647abe1 |
completed | May 2, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 21, 2026, 5 p.m.