Triple
T32965365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zur Kritik der Religion |
E843351
|
entity |
| Predicate | proposesViewOfReligionAs |
P28250
|
FINISHED |
| Object | projection of human essence |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: projection of human essence | Statement: [Zur Kritik der Religion, proposesViewOfReligionAs, projection of human essence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposesViewOfReligionAs Context triple: [Zur Kritik der Religion, proposesViewOfReligionAs, projection of human essence]
-
A.
portraysReligionAs
chosen
Indicates that one entity represents, depicts, or characterizes a religion in a particular way.
-
B.
positionInReligion
Indicates the specific role, rank, or office an entity holds within a religious organization or tradition.
-
C.
hadViewOnReligion
Indicates that an entity held a particular perspective, belief, or stance regarding religion.
-
D.
religionOrBelief
Indicates that one entity holds, practices, or is associated with a particular religion, faith, or belief system.
-
E.
religiousAttitude
Indicates an entity’s stance, disposition, or orientation toward religion or religious beliefs.
- F. None of above.
Provenance (3 batches)
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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: May 1, 2026, 1:21 a.m.