Triple
T12802111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flint cultural institutions network |
E306045
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nonprofit 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: nonprofit collaboration Context triple: [Flint cultural institutions network, instanceOf, nonprofit collaboration]
-
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.
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.
-
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.
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.
-
E.
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.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:30 p.m.