Triple
T29107935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UniProt Consortium |
E736816
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | non-profit collaboration |
C12274
|
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: non-profit collaboration Context triple: [UniProt Consortium, instanceOf, non-profit collaboration]
-
A.
nonprofit project
A nonprofit project is a coordinated set of activities and resources organized to achieve a specific social, cultural, or environmental mission without the primary goal of generating profit.
-
B.
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.
-
C.
public-sector collaboration
Public-sector collaboration is the coordinated effort among government agencies and public institutions, often with private and nonprofit partners, to jointly design, implement, and manage policies or services that address shared societal challenges.
-
D.
collaborative project
chosen
A collaborative project is a coordinated effort in which multiple individuals or groups work together, sharing responsibilities, resources, and expertise to achieve a common goal.
-
E.
community-based partnership
A community-based partnership is a collaborative relationship between local organizations, residents, and stakeholders who share resources, decision-making, and responsibilities to address community needs and achieve mutually beneficial goals.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 11:16 a.m.