Triple
T14890482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACM SIGCHI awards program |
E359741
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ACM SIGCHI activity |
C34546
|
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: ACM SIGCHI activity Context triple: [ACM SIGCHI awards program, instanceOf, ACM SIGCHI activity]
-
A.
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.
-
B.
ACM SIGPLAN event
An ACM SIGPLAN event is a professional gathering—such as a conference, workshop, or symposium—organized under ACM’s Special Interest Group on Programming Languages to present, discuss, and advance research and practice in programming languages and related areas.
-
C.
committee of the Association for Computing Machinery
A committee of the Association for Computing Machinery is a formally organized group of ACM members tasked with overseeing and advancing specific activities, policies, or areas of interest within the computing community.
-
D.
computing education research conference
A computing education research conference is a scholarly gathering where researchers, educators, and practitioners present and discuss empirical and theoretical work on how people learn computing and how to improve the teaching of computing.
-
E.
human–computer interaction expert
A human–computer interaction expert is a specialist who studies, designs, and evaluates interactive systems to optimize how people perceive, use, and experience digital technologies.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 2:10 a.m.