Triple
T25425397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSE |
E637103
|
entity |
| Predicate | addsRegisterClass |
P158292
|
FINISHED |
| Object | XMM0–XMM7 in 32-bit mode |
—
|
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: XMM0–XMM7 in 32-bit mode | Statement: [SSE, addsRegisterClass, XMM0–XMM7 in 32-bit mode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsRegisterClass Context triple: [SSE, addsRegisterClass, XMM0–XMM7 in 32-bit mode]
-
A.
addsClass
Indicates that one entity introduces or appends a class (such as a classification, type, or code) to another entity.
-
B.
addsProtectedClass
Indicates that an action or rule introduces a new protected class or category into a set of legally or formally safeguarded groups.
-
C.
registerType
Indicates that an entity is classified or recorded under a specific type or category within a registration system.
-
D.
registrationOfPrototype
Indicates that an entity is the act or record of officially registering a prototype with a relevant authority or system.
-
E.
usesClass
Indicates that one entity makes use of, depends on, or is implemented using a particular class in its structure or behavior.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6bfdb748190abfd40ed1838d9aa |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 21, 2026, 1:57 p.m.