Triple
T35951072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 42 Helsinki |
E1039726
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | software engineering school |
C1069
|
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: software engineering school Context triple: [42 Helsinki, instanceOf, software engineering school]
-
A.
computer science school
chosen
A computer science school is an educational institution or program dedicated to teaching the principles, theories, and practical skills of computing, programming, and information technology.
-
B.
software engineering program
A software engineering program is a structured course of study that teaches the principles, methods, and tools for designing, developing, testing, and maintaining reliable and efficient software systems.
-
C.
engineering degree program
An engineering degree program is a structured course of study at a college or university that combines mathematics, science, and applied engineering principles to prepare students for professional engineering practice in a specific discipline.
-
D.
software engineering certification
A software engineering certification is a formal credential that validates an individual's knowledge, skills, and competence in applying software engineering principles, practices, and tools to professional development projects.
-
E.
engineering education system
An engineering education system is an organized framework of curricula, instructional methods, resources, and assessment practices designed to develop learners’ technical knowledge, problem-solving skills, and professional competencies in engineering disciplines.
- 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_69f76e25ea488190b7cee970b3e70382 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.