Triple
T25177359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Socket M |
E630483
|
entity |
| Predicate | fsbSupportRange |
P25150
|
FINISHED |
| Object | 533 MT/s |
—
|
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: 533 MT/s | Statement: [Socket M, fsbSupportRange, 533 MT/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fsbSupportRange Context triple: [Socket M, fsbSupportRange, 533 MT/s]
-
A.
supportsSingleRange
Indicates that an entity can handle or operate over only one continuous range of values or positions at a time.
-
B.
frameworkSupport
Indicates that one entity provides compatibility with, or operational support for, a particular framework used by another entity.
-
C.
operationalRange
chosen
Indicates the span of conditions (such as distance, time, or environment) within which a system, device, or process can function effectively and safely.
-
D.
supportsMultipleRanges
Indicates that an entity can handle, accept, or operate over more than one distinct range of values or intervals.
-
E.
isoRangeNative
Indicates that two values fall within the same native ISO-defined range or interval, according to the system’s inherent ISO-based scale or categorization.
- 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46dc1ddd0819089722f45adc50d84 |
completed | May 1, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 12:34 p.m.