Triple
T17022884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ILLIAC I |
E412988
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | engineering research computer |
C21988
|
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: engineering research computer Context triple: [ILLIAC I, instanceOf, engineering research computer]
-
A.
research computer system
chosen
A research computer system is a specialized computing environment designed to support complex scientific or academic investigations by providing high-performance processing, large-scale data storage, and advanced analytical tools.
-
B.
computer science research center
A computer science research center is an institution dedicated to advancing knowledge and innovation in computing through focused research, collaboration, and dissemination of results across areas such as algorithms, systems, artificial intelligence, and human-computer interaction.
-
C.
electronics research laboratory
An electronics research laboratory is a specialized facility equipped with advanced instruments and tools where scientists and engineers design, prototype, and experimentally investigate electronic components, circuits, and systems.
-
D.
computer engineering department
A computer engineering department is an academic unit that focuses on the study, research, and teaching of hardware-software systems, including computer architecture, embedded systems, digital design, and related technologies.
-
E.
computer science community
A computer science community is a group of people who share knowledge, collaborate, and support each other around topics in computing, programming, and related technologies.
- F. None of above.
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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:33 a.m.