Triple
T36026043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of Satan |
E1042129
|
entity |
| Predicate | hasCritics |
P3619
|
FINISHED |
| Object | Christian organizations |
—
|
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: Christian organizations | Statement: [Church of Satan, hasCritics, Christian organizations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCritics Context triple: [Church of Satan, hasCritics, Christian organizations]
-
A.
hasNotableCritic
Indicates that one entity serves as a significant or widely recognized critic of another entity.
-
B.
hasCriticism
chosen
Indicates that one entity expresses disapproval, objection, or negative evaluation directed toward another entity.
-
C.
hasMetacriticRecognition
Indicates that an entity has received recognition, rating, or acknowledgment from Metacritic, typically through inclusion, scoring, or listing on the Metacritic platform.
-
D.
usesCriticCount
Indicates that something bases its evaluation, decision, or outcome on the number of critics involved.
-
E.
hasTheatricalCriticism
Indicates that one entity has written, produced, or is otherwise associated with theatrical criticism about another entity.
- 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_69f76e2c568881909e1e21f85252b0f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: May 3, 2026, 4:07 p.m.