Triple
T17674327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European school of programming language design |
E440605
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tradition in computer science |
C24280
|
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: tradition in computer science Context triple: [European school of programming language design, instanceOf, tradition in computer science]
-
A.
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.
-
B.
historical influence on computing
Historical influence on computing encompasses the people, events, technologies, and social forces from the past that have shaped the development, adoption, and evolution of computer systems and concepts over time.
-
C.
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.
-
D.
research computer system
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.
-
E.
subfield of computer science
chosen
A subfield of computer science is a specialized area of study and research within the broader discipline that focuses on a particular set of concepts, techniques, and applications, such as artificial intelligence, computer graphics, or cybersecurity.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10 a.m.