Triple
T29986947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE membership grades |
E761757
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | professional membership hierarchy |
C15047
|
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 membership hierarchy Context triple: [IEEE membership grades, instanceOf, professional membership hierarchy]
-
A.
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.
-
B.
professional fellowship
A professional fellowship is a structured, time-bound program that provides individuals with advanced training, mentorship, and practical experience in a specific field to develop their expertise and leadership.
-
C.
honorary membership grade
An honorary membership grade is a special, typically non-voting class of membership conferred by an organization to recognize individuals for distinguished service, achievement, or contribution without requiring them to meet standard membership criteria.
-
D.
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.
-
E.
membership category
chosen
A membership category is a defined grouping within an organization or system that specifies a set of shared attributes, rights, and obligations for its members.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:37 p.m.