Triple
T25425840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Socket 8 |
E637112
|
entity |
| Predicate | usedInSystemType |
P18110
|
FINISHED |
| Object | dual-processor servers |
—
|
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: dual-processor servers | Statement: [Socket 8, usedInSystemType, dual-processor servers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInSystemType Context triple: [Socket 8, usedInSystemType, dual-processor servers]
-
A.
usedInType
chosen
Indicates that something serves as a component, element, or example within a particular type or category.
-
B.
usedBySystem
Indicates that something is utilized or operated by a particular system.
-
C.
systemUsedBy
Indicates that a particular system is utilized or operated by a specified agent or user.
-
D.
usedInConflictType
Indicates that something (such as a resource, method, or capability) is employed or applied within a specific type or category of conflict.
-
E.
usedOnPlatformType
Indicates that something is utilized or operates on a specific type of platform.
- 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_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 21, 2026, 1:57 p.m.