Triple
T13067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE Member and Geographic Activities |
E262
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member services organization |
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: member services organization Context triple: [IEEE Member and Geographic Activities, instanceOf, member services organization]
-
A.
nonprofit organization
A nonprofit organization is an entity formed for purposes other than generating profit, using any surplus revenues to further its mission or public benefit rather than distributing them to owners or shareholders.
-
B.
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.
-
C.
learned society
A learned society is an organization that exists to promote an academic discipline or group of related disciplines through research, communication, and professional collaboration among scholars and practitioners.
-
D.
university association
A university association is an organized group within a higher education institution that brings together students, staff, or alumni around shared academic, professional, cultural, or social interests to provide support, activities, and representation.
-
E.
municipality
A municipality is a local administrative unit, such as a city, town, or district, governed by elected officials and responsible for providing public services and regulations within its defined geographic area.
- 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_69a23d7ad88c8190bffe8ab091d86642 |
completed | Feb. 28, 2026, 12:57 a.m. |
Created at: Feb. 28, 2026, 1:02 a.m.