Triple
T35144196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pym van Dyne Foundation |
E1014775
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional philanthropic organization |
C28402
|
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: fictional philanthropic organization Context triple: [Pym van Dyne Foundation, instanceOf, fictional philanthropic organization]
-
A.
philanthropic institution
chosen
A philanthropic institution is an organized entity that mobilizes and distributes resources—financial, material, or human—to support charitable causes and promote social welfare, often guided by a specific mission or set of values.
-
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.
fictional company
A fictional company is an imagined business entity created for storytelling, simulation, or illustrative purposes, complete with its own brand, structure, and operations but without real-world legal or commercial existence.
-
D.
fictional legal person
A fictional legal person is an entity, such as a corporation or organization, that the law recognizes as having legal rights and responsibilities similar to those of a natural person, despite not being a human being.
-
E.
philanthropic fund
A philanthropic fund is a pooled financial resource established to provide ongoing monetary support for charitable causes, social initiatives, or public-benefit projects.
- 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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.