Triple
T3414138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACM SIGPLAN Programming Languages Achievement Award |
E71967
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | programming languages award |
C5392
|
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: programming languages award Context triple: [ACM SIGPLAN Programming Languages Achievement Award, instanceOf, programming languages award]
-
A.
software development award
chosen
A software development award is a formal recognition given to individuals, teams, or organizations for outstanding achievements, innovation, or excellence in creating, maintaining, or improving software products and development practices.
-
B.
programming language
A programming language is a formal system of syntax and semantics that allows humans to write instructions a computer can execute to perform specific tasks or solve problems.
-
C.
cryptography award
A cryptography award is a formal recognition given to individuals or groups for significant contributions, innovations, or achievements in the field of cryptography and information security.
-
D.
economics award program
An economics award program is an organized initiative that recognizes and rewards outstanding achievements, research, or contributions in the field of economics through prizes, honors, or scholarships.
-
E.
programming language implementation
A programming language implementation is the concrete realization of a language’s specification, including its compiler or interpreter, runtime system, and associated tools that translate and execute programs written in that language.
- 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_69ad85ac312481909e7027ced1456a9f |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:15 p.m.