Triple
T23993379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIT course 2.70/2.007 design competition |
E605126
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | engineering design competition |
C35677
|
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: engineering design competition Context triple: [MIT course 2.70/2.007 design competition, instanceOf, engineering design competition]
-
A.
design competition
chosen
A design competition is an organized event where individuals or teams submit creative design solutions to a defined brief, which are then evaluated and ranked by judges based on specified criteria.
-
B.
architectural competition
An architectural competition is a formal process in which architects submit design proposals in response to a defined brief, with entries evaluated to select a winning scheme for potential commissioning.
-
C.
innovation competition
An innovation competition is an organized event where individuals or teams propose and develop novel ideas or solutions to address specific challenges, typically competing for recognition, funding, or other rewards.
-
D.
robotics competition
A robotics competition is an organized event where teams design, build, and program robots to complete specific tasks or challenges under defined rules and constraints.
-
E.
student research competition
A student research competition is an event where students present original research projects to be evaluated and ranked by judges based on criteria such as innovation, rigor, and impact.
- 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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 17, 2026, 9:37 p.m.