Triple
T26351604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silvermont |
E662914
|
entity |
| Predicate | ISAExtension |
P74574
|
FINISHED |
| Object | x86-64 |
—
|
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: x86-64 | Statement: [Silvermont, ISAExtension, x86-64]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISAExtension Context triple: [Silvermont, ISAExtension, x86-64]
-
A.
definesExtension
Indicates that one entity specifies or establishes the extension, scope, or detailed form of another entity.
-
B.
extensionName
Indicates the specific name assigned to an extension associated with an entity or resource.
-
C.
extensionType
Indicates the specific kind or category of extension that characterizes how something is extended or augmented beyond its base form.
-
D.
formerExtension
Indicates that one entity previously served as an extension or subsidiary part of another entity, but no longer holds that status.
-
E.
instructionSetExtension
chosen
Indicates that one instruction set architecture extends or augments another with additional instructions or capabilities.
- 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60fec2c3c8190b76c15fa8a97f0e6 |
completed | May 2, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:45 p.m.