Triple
T22180759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACM-GAMM joint committee |
E548161
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | computer science committee |
C7265
|
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: computer science committee Context triple: [ACM-GAMM joint committee, instanceOf, computer science committee]
-
A.
computer science community
A computer science community is a group of people who share knowledge, collaborate, and support each other around topics in computing, programming, and related technologies.
-
B.
committee of the Association for Computing Machinery
chosen
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.
-
C.
college committee
A college committee is a formally organized group within a college composed of faculty, staff, and sometimes students, tasked with deliberating on specific academic or administrative issues and making recommendations or decisions to support institutional governance and operations.
-
D.
research committee
A research committee is a group of appointed individuals responsible for evaluating, guiding, and overseeing research activities, proposals, and policies within an organization or institution.
-
E.
computer science academic
A computer science academic is a scholar who conducts research, teaches, and advances knowledge in areas such as algorithms, systems, theory, and applications of computing.
- 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_69e11e3d53f88190a2b690e3f25bb062 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:35 p.m.