Triple
T6673757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACM Members-at-Large |
E151798
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ACM governance position |
C10269
|
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 governance position Context triple: [ACM Members-at-Large, instanceOf, ACM governance position]
-
A.
governance position
A governance position is a formal role within an organization or institution responsible for overseeing decision-making, setting policies, and ensuring accountability and compliance with established rules and objectives.
-
B.
IEEE governance role
An IEEE governance role is a leadership or oversight position within the IEEE organization responsible for setting policies, guiding strategic direction, and ensuring effective, ethical operation of its activities and resources.
-
C.
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.
-
D.
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.
-
E.
governing body members
chosen
Individuals who hold official positions within a governing body and are responsible for making, interpreting, or enforcing policies and decisions on behalf of an organization, community, or state.
- 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_69c687f830bc81909eb8b04dbb8450b1 |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 2:03 p.m.