Triple
T21457399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIT Project MAC |
E529378
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | computer science research project |
C120
|
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: computer science research project Context triple: [MIT Project MAC, instanceOf, computer science research project]
-
A.
computer development project
A computer development project is a structured initiative to design, build, test, and deploy computer-based systems or software to meet specific user or business requirements.
-
B.
computer science research center
A computer science research center is an institution dedicated to advancing knowledge and innovation in computing through focused research, collaboration, and dissemination of results across areas such as algorithms, systems, artificial intelligence, and human-computer interaction.
-
C.
research project
chosen
A research project is a structured, systematic investigation designed to answer specific questions or test hypotheses by collecting, analyzing, and interpreting data within a defined scope and timeframe.
-
D.
computer science problem
A computer science problem is a well-defined computational task or question that requires designing algorithms, data structures, or formal methods to determine a solution or prove properties about its solvability or complexity.
-
E.
computer science academic
A computer science academic is a scholar who conducts research, teaches, and advances knowledge in areas such as algorithms, systems, theory, and applications of computing.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:08 p.m.