Triple
T22793430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honeywell Computer Division |
E564176
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defunct computer hardware company division |
C46833
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: defunct computer hardware company division Context triple: [Honeywell Computer Division, instanceOf, defunct computer hardware company division]
-
A.
minicomputer manufacturer
A minicomputer manufacturer is a company that designs, produces, and sells mid-sized computers that offer greater processing power than microcomputers but are smaller and less expensive than mainframes, typically serving business, scientific, or industrial applications.
-
B.
defunct brand
A defunct brand is a formerly active commercial name, trademark, or product line that has been discontinued and is no longer marketed or supported by its owner.
-
C.
semiconductor company division
A semiconductor company division is an organizational unit within a semiconductor firm responsible for specific product lines, technologies, or market segments, managing everything from design and development to marketing and support for its assigned portfolio.
-
D.
division of Electronic Arts
A division of Electronic Arts is an organizational unit within the company responsible for specific functions such as game development, publishing, or support services under the broader EA corporate structure.
-
E.
Intel subsidiary
An Intel subsidiary is a legally distinct company that is majority-owned and controlled by Intel Corporation to support its strategic, operational, or market objectives.
- F. None of above. chosen
Provenance (1 batch)
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_69e2458185f88190b0045227ee420411 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:30 p.m.