Triple
T3796763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Software Engineering Institute |
E91588
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | software engineering research center |
C425
|
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 research center Context triple: [Software Engineering Institute, instanceOf, software engineering research center]
-
A.
research center program
A research center program is an organized initiative within a research institution that coordinates projects, resources, and collaborations to advance inquiry and innovation in a specific field or set of related disciplines.
-
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.
human–computer interaction research center
A human–computer interaction research center is an interdisciplinary organization that studies, designs, and evaluates interactive technologies to improve how people use and experience computer systems.
-
D.
research and development organization
chosen
A research and development organization is an entity dedicated to systematically investigating ideas and technologies to create new knowledge, products, or processes and improve existing ones.
-
E.
research and engagement centre
A research and engagement centre is an institution that conducts systematic inquiry into specific fields while actively collaborating with and involving stakeholders or communities to apply, share, and co-create knowledge.
- 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_69aed96354f48190a768966d6bd19b04 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.