Triple
T3450638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PLDI Student Research Competition |
E72784
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | student research competition |
C12752
|
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: student research competition Context triple: [PLDI Student Research Competition, instanceOf, student research competition]
-
A.
competition section
A competition section is a designated part of an event, document, or platform that organizes, presents, and manages information, rules, and results related to specific contests or competitive activities.
-
B.
undergraduate research program
An undergraduate research program is a structured academic initiative that engages undergraduate students in faculty-mentored, inquiry-based projects to develop research skills, deepen disciplinary knowledge, and foster scholarly or creative contributions.
-
C.
research project
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.
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.
competitive funding program
A competitive funding program is a structured process in which individuals or organizations submit proposals to vie for limited financial resources, with awards granted based on predefined criteria and comparative merit.
- F. None of above. chosen
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_69ad85b05c848190b7a28ceec2bd7b74 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:16 p.m.