Triple
T25931513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Sandy Bridge |
E653448
|
entity |
| Predicate | frontSideBusReplacement |
P160699
|
FINISHED |
| Object | DMI 2.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: DMI 2.0 | Statement: [Intel Sandy Bridge, frontSideBusReplacement, DMI 2.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontSideBusReplacement Context triple: [Intel Sandy Bridge, frontSideBusReplacement, DMI 2.0]
-
A.
frontSideBus
Indicates a connection where one component communicates with another over the primary data pathway (front-side bus) between a processor and the rest of the system.
-
B.
accessByBusFrom
Indicates that one location can be reached from another location using a bus as the mode of transportation.
-
C.
hasBusInterchange
Indicates that one transport-related entity includes, contains, or is associated with a bus interchange facility.
-
D.
replacedRide
Indicates that one ride has been substituted for or taken the place of another ride.
-
E.
openedForBusService
Indicates that a facility, route, or location has begun operating and is available for use by public bus services.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60459a53c8190bbd90e80890eebcd |
completed | May 2, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f603b90c94819088d62cb9489e95ff |
completed | May 2, 2026, 2:01 p.m. |
Created at: April 22, 2026, 8:37 a.m.