Triple
T7304695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSSE3 |
E167944
|
entity |
| Predicate | firstSupportedMicroarchitecture |
P76107
|
FINISHED |
| Object | Intel Core microarchitecture |
—
|
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: Intel Core microarchitecture | Statement: [SSSE3, firstSupportedMicroarchitecture, Intel Core microarchitecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSupportedMicroarchitecture Context triple: [SSSE3, firstSupportedMicroarchitecture, Intel Core microarchitecture]
-
A.
firstSupportedCPUCore
Indicates the CPU core that initially provided support or capability for a given feature, process, or entity.
-
B.
firstSupportedCPUFamily
Indicates the earliest CPU family that a system, software, or feature is designed to support or is compatible with.
-
C.
firstSupportedBy
Indicates that an entity is initially upheld, enabled, or made possible by another entity that provides its primary support.
-
D.
laterSupportedArchitecture
Indicates that one architecture provides support for another architecture that was introduced or adopted at a later time.
-
E.
cpuCoreMicroarchitecture
Indicates the specific microarchitecture design implemented in a given CPU core.
- 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebd61c0c8190abb1368c9dfb1550 |
completed | March 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb2d4c0c8190b4cc6fdfdb7f4827 |
completed | March 27, 2026, 8:40 p.m. |
Created at: March 27, 2026, 3:01 p.m.