Triple
T25564683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Haswell microarchitecture |
E640802
|
entity |
| Predicate | supportsMemoryChannelCount |
P82796
|
FINISHED |
| Object | dual-channel |
—
|
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: dual-channel | Statement: [Intel Haswell microarchitecture, supportsMemoryChannelCount, dual-channel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMemoryChannelCount Context triple: [Intel Haswell microarchitecture, supportsMemoryChannelCount, dual-channel]
-
A.
maxMemoryChannels
Indicates the maximum number of memory channels that an entity can support or utilize.
-
B.
hasChannelCount
chosen
Indicates that an entity is associated with a specific number of channels.
-
C.
numberOfAdditionalChannels
Indicates the quantity of extra channels added beyond a base or default set in a given context.
-
D.
hasNumberOfADPCMAChannels
Indicates the quantity of ADPCM (Adaptive Differential Pulse-Code Modulation) channels associated with or supported by an entity.
-
E.
supportsChannels
Indicates that one entity is capable of handling, providing, or being compatible with one or more specified channels for communication, distribution, or operation.
- 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_69e75dc1beb08190bac7d76b8d6e7bc4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 21, 2026, 3:48 p.m.