Triple
T32988230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PS/2 |
E844005
|
entity |
| Predicate | cpuUsedInSomeModels |
P99156
|
FINISHED |
| Object | Intel 8086 |
—
|
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 8086 | Statement: [PS/2, cpuUsedInSomeModels, Intel 8086]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cpuUsedInSomeModels Context triple: [PS/2, cpuUsedInSomeModels, Intel 8086]
-
A.
usedInDeviceModel
chosen
Indicates that something (such as a component, material, or technology) is utilized within or incorporated into a particular device model.
-
B.
compatibilityModel
Indicates that one entity is defined or evaluated according to a specific compatibility framework, standard, or model in relation to another entity.
-
C.
usesProductionModel
Indicates that one entity employs or relies on another entity as its primary or official production model in practice.
-
D.
hardwareUsedBy
Indicates that a piece of hardware is utilized or operated by a particular entity (such as a person, system, or organization).
-
E.
usedWithChipsetsFrom
Indicates that something is designed or suitable to be used together with specific chipsets from a given manufacturer or family.
- 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d210fc80819091ed8961aa2cddfb |
completed | May 3, 2026, 4:41 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:22 a.m.