Triple
T34789531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Low Church Anglicanism |
E1002906
|
entity |
| Predicate | oftenRejects |
P19799
|
FINISHED |
| Object | doctrine of transubstantiation |
—
|
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: doctrine of transubstantiation | Statement: [Low Church Anglicanism, oftenRejects, doctrine of transubstantiation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenRejects Context triple: [Low Church Anglicanism, oftenRejects, doctrine of transubstantiation]
-
A.
mayReject
Indicates that one entity has the authority or option to refuse, decline, or not accept another entity or proposal.
-
B.
typicallyDenies
chosen
Indicates that an entity, in most usual or common circumstances, refuses, rejects, or does not grant something to another entity.
-
C.
rarelyRefused
Indicates that an action, request, or offer is almost always accepted and only infrequently declined.
-
D.
canRejectWith
Indicates that one entity has the authority or ability to refuse, decline, or dismiss another entity or proposal using a specific method or condition.
-
E.
rejectedIn
Indicates that an entity or proposal was not accepted or was turned down within a specific context, process, or location.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: May 3, 2026, 3:59 p.m.