Triple
T9027115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel SSE |
E216074
|
entity |
| Predicate | addsRegisterFile |
P4184
|
FINISHED |
| Object | XMM registers |
—
|
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: XMM registers | Statement: [Intel SSE, addsRegisterFile, XMM registers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsRegisterFile Context triple: [Intel SSE, addsRegisterFile, XMM registers]
-
A.
registerFile
Indicates that an entity records or stores information about a file in some kind of registry or tracking system.
-
B.
registerFileUsed
Indicates that a particular register file is utilized or accessed in the given context or operation.
-
C.
relatedRegister
Indicates a relationship where one entity is associated with, linked to, or corresponds to a particular register or record in a system.
-
D.
hasRegister
chosen
Indicates that one entity possesses, contains, or is associated with a specific register (such as a record, log, or hardware register).
-
E.
registryFunction
Indicates a function that is responsible for registering or recording entities, configurations, or events within a registry or central management system.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7eb5b881908ace0c3327f06161 |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.