Triple
T26006871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Socket 754 |
E646783
|
entity |
| Predicate | frontSideBusType |
P99927
|
FINISHED |
| Object | HyperTransport |
—
|
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: HyperTransport | Statement: [Socket 754, frontSideBusType, HyperTransport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontSideBusType Context triple: [Socket 754, frontSideBusType, HyperTransport]
-
A.
frontSideBus
chosen
Indicates a connection where one component communicates with another over the primary data pathway (front-side bus) between a processor and the rest of the system.
-
B.
frontSideBusReplacement
Indicates that one front side bus has been replaced by another in a system or configuration.
-
C.
frontType
Indicates the type or category of a front (e.g., boundary or leading side) that one entity presents or forms relative to another.
-
D.
frontSightType
Indicates the specific kind or design of the front sight used on an object, typically a firearm or similar aiming device.
-
E.
typeOfFront
Indicates that one entity is a specific kind or category of front (e.g., weather or battle front) relative to another.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 22, 2026, 9:01 a.m.