Triple
T430916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Immaculate Conception |
E9709
|
entity |
| Predicate | notAcceptedBy |
P438
|
FINISHED |
| Object | most Protestant denominations |
—
|
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: most Protestant denominations | Statement: [Immaculate Conception, notAcceptedBy, most Protestant denominations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notAcceptedBy Context triple: [Immaculate Conception, notAcceptedBy, most Protestant denominations]
-
A.
notRecognizedBy
Indicates that one entity does not acknowledge, accept, or formally recognize the status, authority, or validity of another entity.
-
B.
notRecommendedBy
Indicates that one entity explicitly advises against or does not endorse another entity.
-
C.
rejectedBy
chosen
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
D.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
E.
rejectedOrModifiedBy
Indicates that a proposal, request, or item was either not accepted as-is or was altered by a particular agent or authority.
- 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eeef065c81908ed30528a61da132 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd9264c8190b92f9a50348e5541 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.