Triple
T33555816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM Cambridge Scientific Center |
E859469
|
entity |
| Predicate | usedHardwarePlatform |
P12755
|
FINISHED |
| Object | IBM System/360 |
—
|
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: IBM System/360 | Statement: [IBM Cambridge Scientific Center, usedHardwarePlatform, IBM System/360]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedHardwarePlatform Context triple: [IBM Cambridge Scientific Center, usedHardwarePlatform, IBM System/360]
-
A.
usedPlatformType
Indicates that an entity makes use of or operates on a particular type or category of platform.
-
B.
hardwarePlatformFor
Indicates that one entity serves as the hardware platform on which another entity is designed to run or be deployed.
-
C.
hardwareUsed
Indicates that a particular piece of hardware is utilized or employed in performing an action, process, or function involving another entity.
-
D.
hardwareUsedBy
chosen
Indicates that a piece of hardware is utilized or operated by a particular entity (such as a person, system, or organization).
-
E.
usedByPlatform
Indicates that something (such as a tool, component, or resource) is utilized or employed by a particular 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_69f3497b2b68819093207971b5e13dc8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f70d13688190be673ad55e48bdcc |
completed | May 3, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:40 a.m.