Triple

T17017411
Position Surface form Disambiguated ID Type / Status
Subject ACM SIGSOFT awards program E412858 entity
Predicate instanceOf P0 FINISHED
Object ACM SIGSOFT activity C38649 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 SIGSOFT activity
Context triple: [ACM SIGSOFT awards program, instanceOf, ACM SIGSOFT activity]
  • A. 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.
  • B. ACM SIGCHI activity
    An ACM SIGCHI activity is an organized event, initiative, or program sponsored or endorsed by the ACM Special Interest Group on Computer-Human Interaction to advance research, practice, and community engagement in human-computer interaction.
  • 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. ACM program
    An ACM program is a software application or system developed, evaluated, or used within the context of the Association for Computing Machinery’s computing, research, and educational activities.
  • 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_69d886cc4170819093deddc7b8b4b6a7 completed April 10, 2026, 5:12 a.m.
Created at: April 10, 2026, 5:33 a.m.