Triple
T31663318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Why Women Need the Goddess |
E808060
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | feminist theological work |
C22562
|
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: feminist theological work Context triple: [Why Women Need the Goddess, instanceOf, feminist theological work]
-
A.
theological work
A theological work is a written or spoken scholarly exploration that systematically examines, interprets, and articulates beliefs about the nature of the divine, religious doctrines, and their implications for faith and practice.
-
B.
feminist work
chosen
A feminist work is a creation—such as a text, artwork, performance, or project—intentionally designed to critique gender-based power structures and advocate for equity, agency, and the reimagining of social relations from feminist perspectives.
-
C.
theological journal
A theological journal is a periodical publication that presents scholarly research, critical essays, and reflections on religious beliefs, doctrines, practices, and their implications for faith and society.
-
D.
feminist scholar
A feminist scholar is an academic who critically examines gender, power, and inequality, producing theory and research aimed at understanding and transforming oppressive social structures.
-
E.
ecofeminist work
An ecofeminist work is a creative or scholarly piece that explores the interconnected oppressions of women and nature, critiquing patriarchal and exploitative systems while envisioning more just, sustainable, and relational ways of living.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:58 p.m.