Triple
T25425837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Socket 8 |
E637112
|
entity |
| Predicate | supportsBusType |
P24486
|
FINISHED |
| Object | Intel GTL+ front-side bus |
—
|
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: Intel GTL+ front-side bus | Statement: [Socket 8, supportsBusType, Intel GTL+ front-side bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBusType Context triple: [Socket 8, supportsBusType, Intel GTL+ front-side bus]
-
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.
supportsType
chosen
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
C.
supportsTestType
Indicates that one entity is capable of handling, executing, or being compatible with a specified type of test.
-
D.
supportsDriverType
Indicates that one entity is compatible with, or able to operate using, a specified type of driver.
-
E.
supportsProgramType
Indicates that one entity is capable of handling, offering, or being compatible with a specified type of program.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 21, 2026, 1:57 p.m.