Triple
T14152853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UltraSPARC T1 |
E350729
|
entity |
| Predicate | coherencyProtocol |
P74577
|
FINISHED |
| Object | directory-based cache coherence |
—
|
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: directory-based cache coherence | Statement: [UltraSPARC T1, coherencyProtocol, directory-based cache coherence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coherencyProtocol Context triple: [UltraSPARC T1, coherencyProtocol, directory-based cache coherence]
-
A.
cacheCoherencyProtocol
chosen
Indicates that a specific protocol is used to maintain consistency of cached data across multiple processors or cache levels in a system.
-
B.
consistencyModel
Indicates that one entity adheres to, implements, or is governed by a particular consistency model in its behavior or operations.
-
C.
memoryModel
Indicates a relationship where an entity serves as or uses a specific model or framework for representing, organizing, or managing memory.
-
D.
isCooperative
Indicates that an entity engages willingly and constructively in joint actions or relationships with others, working together toward shared goals.
-
E.
successorProtocol
Indicates that one protocol directly follows and replaces another in sequence or versioning.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6133754881908e1e97db71772deb |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:57 a.m.