Triple
T7033051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Pentium Pro |
E163313
|
entity |
| Predicate | cacheCoherencyProtocol |
P74577
|
FINISHED |
| Object | MESI |
—
|
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: MESI | Statement: [Intel Pentium Pro, cacheCoherencyProtocol, MESI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cacheCoherencyProtocol Context triple: [Intel Pentium Pro, cacheCoherencyProtocol, MESI]
-
A.
consistencyModel
Indicates that one entity adheres to, implements, or is governed by a particular consistency model in its behavior or operations.
-
B.
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.
-
C.
L1Cache
Indicates a relationship where data or instructions are stored or accessed in the first-level (closest, fastest) cache memory associated with a processor core.
-
D.
cacheType
Indicates the specific kind or category of cache associated with an entity or operation.
-
E.
caches
Indicates that one entity stores data or resources so they can be quickly retrieved for future use by another entity or process.
- 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_69c6885d691c81908cf7d31083113886 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e458ad9c81908c3f492b317ce291 |
completed | March 27, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b9a2488190aea351d96afa5a12 |
completed | March 27, 2026, 7:59 p.m. |
| PDg | Predicate description generation | batch_69c6e456e89481908df42a1b4232a4a0 |
completed | March 27, 2026, 8:11 p.m. |
Created at: March 27, 2026, 2:36 p.m.