Triple
T9263829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASME member |
E222644
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | professional association member |
C7
|
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: professional association member Context triple: [ASME member, instanceOf, professional association member]
-
A.
professional association
chosen
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.
-
B.
position in a professional association
A position in a professional association represents a formally recognized role or office held by a member, defined by specific responsibilities, authority, and term within the association’s organizational structure.
-
C.
professional occupation
A professional occupation is a specialized role in the workforce that requires advanced knowledge, formal training or credentials, and adherence to established standards or ethics to provide expert services in a particular field.
-
D.
professional meeting
A professional meeting is a structured gathering of individuals in a work or organizational context to share information, make decisions, solve problems, or coordinate activities toward defined objectives.
-
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_69ca841f2e808190a64f4c31903a1332 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:32 p.m.