Triple

T26006989
Position Surface form Disambiguated ID Type / Status
Subject Socket AM2 E646785 entity
Predicate supportedBusInterface P193521 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 AM2, supportedBusInterface, HyperTransport]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportedBusInterface
Context triple: [Socket AM2, supportedBusInterface, HyperTransport]
  • A. supportsBusController
    Indicates that one entity provides the necessary functionality or compatibility to operate, manage, or interface with a bus controller for another entity.
  • B. supportedIn
    Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
  • C. supportedAs
    Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
  • D. supportsBusSpeed
    Indicates that one entity is capable of operating at, or is compatible with, a specified bus communication speed of another entity.
  • E. isSupportedBy
    Indicates that an entity is upheld, sustained, or enabled by another entity, which provides necessary assistance, resources, or justification.
  • 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_69e77e89d5848190b54352cdb74f6029 completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69fd49f6dbac81909744373a357b7982 completed May 8, 2026, 2:27 a.m.
PD Predicate disambiguation batch_69fd48ed68f481908374183c66a6b055 completed May 8, 2026, 2:22 a.m.
PDg Predicate description generation batch_69fd49f612a4819096fe7d5a3bb439ba completed May 8, 2026, 2:27 a.m.
Created at: April 22, 2026, 9:01 a.m.