occam programming language
E440672
Occam is a concurrent programming language developed in the early 1980s for the INMOS Transputer, designed around lightweight processes and message-passing communication to support parallel computing.
All labels observed (1)
| Label | Occurrences |
|---|---|
| occam programming language canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T4443701 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: occam programming language Context triple: [CSP (Communicating Sequential Processes), influenced, occam programming language]
-
A.
Oberon programming language
The Oberon programming language is a minimalist, modular, and strongly typed language designed by Niklaus Wirth as the successor to Modula-2, emphasizing simplicity and efficiency in both language and operating system design.
-
B.
Eiffel programming language
Eiffel is an object-oriented programming language designed by Bertrand Meyer that emphasizes software correctness through features like Design by Contract and strong support for modular, reusable code.
-
C.
Algol 68C
Algol 68C is a compiler implementation of the Algol 68 programming language, designed to translate its advanced structured constructs into executable machine code.
-
D.
Algol 68R
Algol 68R is a revised, more practical and implementable version of the Algol 68 programming language, created to simplify and clarify the original language’s complex design.
-
E.
Algol 68S
Algol 68S is a simplified subset of the Algol 68 programming language designed to make the language easier to implement and use.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: occam programming language Target entity description: Occam is a concurrent programming language developed in the early 1980s for the INMOS Transputer, designed around lightweight processes and message-passing communication to support parallel computing.
-
A.
Oberon programming language
The Oberon programming language is a minimalist, modular, and strongly typed language designed by Niklaus Wirth as the successor to Modula-2, emphasizing simplicity and efficiency in both language and operating system design.
-
B.
Eiffel programming language
Eiffel is an object-oriented programming language designed by Bertrand Meyer that emphasizes software correctness through features like Design by Contract and strong support for modular, reusable code.
-
C.
Algol 68C
Algol 68C is a compiler implementation of the Algol 68 programming language, designed to translate its advanced structured constructs into executable machine code.
-
D.
Algol 68R
Algol 68R is a revised, more practical and implementable version of the Algol 68 programming language, created to simplify and clarify the original language’s complex design.
-
E.
Algol 68S
Algol 68S is a simplified subset of the Algol 68 programming language designed to make the language easier to implement and use.
- F. None of above. chosen
Statements (51)
| Predicate | Object |
|---|---|
| instanceOf |
concurrent programming language
ⓘ
programming language ⓘ |
| basedOn | Communicating Sequential Processes NERFINISHED ⓘ |
| designedFor |
INMOS Transputer
NERFINISHED
ⓘ
fine-grained parallelism ⓘ |
| designGoal |
deterministic parallel programming
ⓘ
efficient mapping to Transputer hardware ⓘ high reliability in concurrent systems ⓘ |
| developer |
David May
NERFINISHED
ⓘ
INMOS NERFINISHED ⓘ others at INMOS ⓘ |
| executionModel |
message-passing concurrency
ⓘ
process network ⓘ |
| fileExtension | .occ ⓘ |
| hasKeyword |
ALT
NERFINISHED
ⓘ
CHAN NERFINISHED ⓘ PAR NERFINISHED ⓘ SEQ ⓘ |
| inception | early 1980s ⓘ |
| influenced |
CSP-based concurrency libraries in other languages
ⓘ
Go programming language NERFINISHED ⓘ occam 2 NERFINISHED ⓘ occam 2.1 NERFINISHED ⓘ occam-π NERFINISHED ⓘ |
| influencedBy | CSP NERFINISHED ⓘ |
| inspiredBy | principle of parsimony (Occam's razor) ⓘ |
| memoryManagement | no dynamic memory allocation ⓘ |
| namedAfter | William of Ockham NERFINISHED ⓘ |
| notableFeature |
compile-time checked communication protocols
ⓘ
no shared memory between processes ⓘ very lightweight processes mapped to Transputer hardware ⓘ |
| paradigm |
communicating sequential processes
ⓘ
concurrent ⓘ imperative ⓘ parallel ⓘ |
| primaryUse |
embedded systems on Transputers
ⓘ
parallel computing ⓘ |
| standardizedAs | occam 1 ⓘ |
| successor |
occam 2
NERFINISHED
ⓘ
occam 2.1 NERFINISHED ⓘ occam-π NERFINISHED ⓘ |
| supports |
alternation (ALT construct)
ⓘ
channel-based communication ⓘ deterministic concurrency ⓘ lightweight processes ⓘ message passing ⓘ parallel composition ⓘ sequential composition ⓘ synchronous communication ⓘ |
| typingDiscipline |
static typing
ⓘ
strong typing ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: occam programming language Description of subject: Occam is a concurrent programming language developed in the early 1980s for the INMOS Transputer, designed around lightweight processes and message-passing communication to support parallel computing.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.