Triple
T26105198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSE4.2 |
E658517
|
entity |
| Predicate | registerTypeUsed |
P159140
|
FINISHED |
| Object | XMM |
—
|
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 | Statement: [SSE4.2, registerTypeUsed, XMM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registerTypeUsed Context triple: [SSE4.2, registerTypeUsed, XMM]
-
A.
registerType
Indicates that an entity is classified or recorded under a specific type or category within a registration system.
-
B.
usesRegisterType
chosen
Indicates that one entity employs or relies on a specific type or category of register in its operation or representation.
-
C.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
D.
registerFileUsed
Indicates that a particular register file is utilized or accessed in the given context or operation.
-
E.
hasUsageRegister
Indicates that a linguistic expression is associated with a particular usage register or level of formality in communication.
- 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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60775b298819095c64aca6806d61c |
completed | May 2, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 7:58 p.m.