Triple
T10763425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mathematical Laboratory |
E253890
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical computing organization |
C1884
|
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: historical computing organization Context triple: [Mathematical Laboratory, instanceOf, historical computing organization]
-
A.
historical computer architecture
Historical computer architecture is the study and classification of past computer system designs, components, and organizational principles that shaped the evolution of computing hardware over time.
-
B.
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.
-
C.
historical group
chosen
A historical group is a collection of people connected by a shared identity, purpose, or activity that existed and acted within a specific past time period.
-
D.
committee of the Association for Computing Machinery
A committee of the Association for Computing Machinery is a formally organized group of ACM members tasked with overseeing and advancing specific activities, policies, or areas of interest within the computing community.
-
E.
electronic stored-program computer
An electronic stored-program computer is a digital machine that executes instructions and processes data by electronically manipulating binary information according to programs held in its memory.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:16 p.m.