Triple
T1639830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carnegie Observatories |
E35443
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nonprofit organization unit |
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 organization unit Context triple: [Carnegie Observatories, instanceOf, nonprofit organization unit]
-
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.
advocacy unit
An advocacy unit is an organized group or department dedicated to influencing policies, decisions, or public opinion in support of specific causes or interests.
-
C.
healthcare organization unit
A healthcare organization unit is a distinct administrative or functional division within a healthcare system (such as a department, clinic, or ward) that delivers specific health-related services, manages resources, and supports patient care processes.
-
D.
organizational unit category
An organizational unit category is a classification that groups organizational units based on shared characteristics such as function, structure, or hierarchy to support consistent management and analysis.
-
E.
nonprofit organization program
A nonprofit organization program is a structured set of coordinated activities and services designed and operated by a nonprofit to advance its mission and create specific social, cultural, or environmental impact for a defined target population.
- 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_69a88604618c81908b41f6429c431eb6 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:28 p.m.