Triple
T25616975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Socket A |
E642184
|
entity |
| Predicate | supportedFrontSideBus |
P31519
|
FINISHED |
| Object | 100 MHz |
—
|
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: 100 MHz | Statement: [Socket A, supportedFrontSideBus, 100 MHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedFrontSideBus Context triple: [Socket A, supportedFrontSideBus, 100 MHz]
-
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.
supportsBackplane
Indicates that one entity provides compatibility with or the capability to operate using another entity’s backplane infrastructure.
-
C.
supportsBusSpeed
chosen
Indicates that one entity is capable of operating at, or is compatible with, a specified bus communication speed of another entity.
-
D.
supportsMultipleBusMasters
Indicates that the system or component allows more than one bus master to control or access the bus concurrently or in turn.
-
E.
hasBusArchitecture
Indicates that one entity uses, implements, or is characterized by a particular bus architecture in its design 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 21, 2026, 5 p.m.