Triple
T5601887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACM Secretary/Treasurer |
E147138
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | officer of a professional association |
C11431
|
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: officer of a professional association Context triple: [ACM Secretary/Treasurer, instanceOf, officer of a professional association]
-
A.
member of learned society
A member of a learned society is an individual formally affiliated with an organization dedicated to advancing a specific academic, scientific, or professional field through research, scholarship, and the exchange of knowledge.
-
B.
professional association
A professional association is an organized group of individuals in the same occupation or field that advances shared professional interests through networking, standards, advocacy, and continuing education.
-
C.
organizational representative
chosen
An organizational representative is an individual or entity authorized to act on behalf of an organization in communications, decisions, and formal transactions.
-
D.
member of a board of trustees
A member of a board of trustees is an individual entrusted with overseeing an organization’s governance, policy, and strategic direction while safeguarding its mission and assets on behalf of stakeholders.
-
E.
professional organization committee
A professional organization committee is a structured group of members within a professional body tasked with planning, overseeing, and executing specific functions or initiatives to support the organization’s goals and its stakeholders.
- 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_69c009043d648190a7af89698ccf1e3e |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:39 p.m.