Triple
T26006990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Socket AM2 |
E646785
|
entity |
| Predicate | hyperTransportVersion |
P159659
|
FINISHED |
| Object | HyperTransport 1.0 |
—
|
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 1.0 | Statement: [Socket AM2, hyperTransportVersion, HyperTransport 1.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hyperTransportVersion Context triple: [Socket AM2, hyperTransportVersion, HyperTransport 1.0]
-
A.
supportsPCIeVersion
Indicates that one entity is compatible with or able to operate using a specified version of the PCI Express (PCIe) standard.
-
B.
supportsIntelTurboBoost
Indicates that one entity provides compatibility with or functional support for Intel Turbo Boost technology in relation to another entity.
-
C.
supportsHyperThreading
Indicates that one entity provides or enables Hyper-Threading capability for another entity.
-
D.
hdmiVersion
Indicates the specific HDMI standard or version associated with a device, port, or connection.
-
E.
supportsIntelHyperThreading
Indicates that one entity provides compatibility with or functionality for Intel Hyper-Threading technology in relation to another entity.
- 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_69f6057bd2708190bf400b153aca2f1b |
completed | May 2, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69f4a10728e08190bc0b96c558740f51 |
completed | May 1, 2026, 12:48 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 22, 2026, 9:01 a.m.