Triple
T15775035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tampa Bay community organizations |
E382468
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | network of nonprofit organizations |
C26969
|
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: network of nonprofit organizations Context triple: [Tampa Bay community organizations, instanceOf, network of nonprofit organizations]
-
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.
international non-governmental organization platform
An international non-governmental organization platform is a global, non-state entity that facilitates coordination, collaboration, and resource-sharing among NGOs across countries to address transnational social, environmental, or humanitarian issues.
-
C.
youth organization network
chosen
A youth organization network is a collaborative structure that connects multiple youth-focused groups to share resources, coordinate activities, and amplify young people’s voices and impact.
-
D.
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.
-
E.
network of national bodies
A network of national bodies is a coordinated system of country-level organizations that collaborate, share information, and align actions to address common goals or standards across multiple nations.
- 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:47 a.m.