Triple
T26237917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACS Puget Sound Section |
E656219
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nonprofit scientific organization |
C6
|
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: nonprofit scientific organization Context triple: [ACS Puget Sound Section, instanceOf, nonprofit scientific organization]
-
A.
nonprofit organization
chosen
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.
scientific community organization
A scientific community organization is a structured group that unites researchers and professionals within specific scientific fields to promote collaboration, knowledge exchange, standard-setting, and advancement of the discipline.
-
C.
regional scientific body
A regional scientific body is an organization that coordinates, supports, and promotes scientific research, collaboration, and policy advice within a specific geographic region.
-
D.
division of a scientific society
A division of a scientific society is a specialized subunit within the society that focuses on a particular discipline, topic, or professional interest, organizing activities, research, and member services related to that area.
-
E.
research organization
A research organization is an institution that systematically investigates specific questions or problems to generate new knowledge, technologies, or insights, often within scientific, academic, or applied domains.
- 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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
Created at: April 26, 2026, 9:02 p.m.