Triple
T25550391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AVX |
E640423
|
entity |
| Predicate | firstSupportedInMicroarchitecture |
P76107
|
FINISHED |
| Object | Intel Sandy Bridge |
—
|
NE NERFINISHED |
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: Intel Sandy Bridge | Statement: [AVX, firstSupportedInMicroarchitecture, Intel Sandy Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSupportedInMicroarchitecture Context triple: [AVX, firstSupportedInMicroarchitecture, Intel Sandy Bridge]
-
A.
firstSupportedMicroarchitecture
chosen
Indicates the earliest or oldest microarchitecture that provides support for a given hardware or software feature.
-
B.
firstSupportedCPUCore
Indicates the CPU core that initially provided support or capability for a given feature, process, or entity.
-
C.
firstSupportedCPUFamily
Indicates the earliest CPU family that a system, software, or feature is designed to support or is compatible with.
-
D.
firstSupportedBy
Indicates that an entity is initially upheld, enabled, or made possible by another entity that provides its primary support.
-
E.
laterSupportedArchitecture
Indicates that one architecture provides support for another architecture that was introduced or adopted at a later time.
- 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_69e75dc101a881909fd33b02174e9768 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: April 21, 2026, 3:36 p.m.