Triple
T1042201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laudian religious reforms |
E22492
|
entity |
| Predicate | discouraged |
P2184
|
FINISHED |
| Object | extemporaneous preaching |
—
|
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: extemporaneous preaching | Statement: [Laudian religious reforms, discouraged, extemporaneous preaching]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discouraged Context triple: [Laudian religious reforms, discouraged, extemporaneous preaching]
-
A.
discourages
chosen
Indicates an action or influence that deters, dissuades, or reduces the likelihood of someone performing a particular behavior or pursuing a certain outcome.
-
B.
encourages
Indicates actively motivating, supporting, or giving confidence to another entity to pursue an action, behavior, or state.
-
C.
undermined
Indicates that one entity has weakened, subverted, or reduced the effectiveness, authority, or stability of another entity or its position.
-
D.
disadvantage
Indicates that one entity is in a less favorable, weaker, or hindered position relative to another in a given context.
-
E.
notRecommendedBy
Indicates that one entity explicitly advises against or does not endorse 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b845fa8c8190a7b69629883b62e2 |
completed | March 1, 2026, 10:05 p.m. |
| PD | Predicate disambiguation | batch_69a4b72ba60881908b017ef3b2b9645e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.