Triple
T1422948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel 8086 |
E30264
|
entity |
| Predicate | packageType |
P28919
|
FINISHED |
| Object | 40-pin DIP |
—
|
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: 40-pin DIP | Statement: [Intel 8086, packageType, 40-pin DIP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: packageType Context triple: [Intel 8086, packageType, 40-pin DIP]
-
A.
codeType
Indicates the classification or category assigned to a particular code within a coding or encoding system.
-
B.
componentType
Indicates that one entity specifies or classifies the kind or category of component that another entity represents or uses.
-
C.
deploymentType
Indicates the manner or configuration in which a system, application, or component is deployed or made operational.
-
D.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
E.
programType
Indicates the category or kind of program to which an entity belongs or with which it is associated.
- 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_69a498fb823c8190a67ce4c4837e641a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c52e4ed881908d85e0cb9fe851ac |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c4752abc8190a33b634c4d6fad28 |
completed | March 1, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69a4c52bbb748190aaa804438d31f4c2 |
completed | March 1, 2026, 11 p.m. |
Created at: March 1, 2026, 8 p.m.