Triple
T25177358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Socket M |
E630483
|
entity |
| Predicate | primaryBusInterface |
P32414
|
FINISHED |
| Object | Intel front-side bus |
—
|
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: Intel front-side bus | Statement: [Socket M, primaryBusInterface, Intel front-side bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBusInterface Context triple: [Socket M, primaryBusInterface, Intel front-side bus]
-
A.
primaryBus
chosen
Indicates that one entity functions as the main or principal bus associated with another entity within a system or configuration.
-
B.
primaryInterface
Indicates that one entity serves as the main or default interface through which another entity is accessed or interacted with.
-
C.
primaryApplicationBinaryInterface
Indicates the main binary interface standard that governs how compiled code components interact at the machine level (e.g., function calling, data layout, and linkage) within a given environment.
-
D.
primaryInputOutput
Indicates that one entity serves as the main source or destination of data, signals, or materials for another entity within a process or system.
-
E.
systemBus
Indicates a relationship where a component is connected to or communicates over a shared system-wide communication bus.
- 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_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 21, 2026, 12:34 p.m.