Triple
T36008244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PenFed Foundation (leadership role) |
E1041330
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nonprofit governance role |
C52328
|
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 governance role Context triple: [PenFed Foundation (leadership role), instanceOf, nonprofit governance role]
-
A.
governance position
A governance position is a formal role within an organization or institution responsible for overseeing decision-making, setting policies, and ensuring accountability and compliance with established rules and objectives.
-
B.
position in a non-profit organization
chosen
A position in a non-profit organization is a defined role with specific responsibilities and authority that contributes to advancing the organization’s mission and serving its stakeholders.
-
C.
charity governance structure
A charity governance structure is the organized framework of roles, responsibilities, and decision-making processes that guide how a charitable organization is directed, controlled, and held accountable to its mission and stakeholders.
-
D.
non-executive director
A non-executive director is a member of a company’s board who is not part of the executive management team and provides independent oversight, strategic guidance, and governance without being involved in day-to-day operations.
-
E.
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.
- 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_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.