Triple
T10728589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neo-orthodoxy |
E253013
|
entity |
| Predicate | reactedAgainst |
P437
|
FINISHED |
| Object | liberal Protestant theology |
—
|
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: liberal Protestant theology | Statement: [Neo-orthodoxy, reactedAgainst, liberal Protestant theology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactedAgainst Context triple: [Neo-orthodoxy, reactedAgainst, liberal Protestant theology]
-
A.
reactionType
Indicates the specific kind or category of reaction that occurs between entities or in response to an event or stimulus.
-
B.
relatedReaction
Indicates that one reaction is connected or associated with another reaction in some relevant way.
-
C.
sideReaction
Indicates that one reaction occurs as an unintended or secondary process alongside a primary reaction.
-
D.
opposedBy
chosen
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
E.
usedAgainst
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, 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_69d6aa5d8be481909a43218b2bfdbe95 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d70fc92a18819089cc67afee1c9b96 |
completed | April 9, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69d6f309a44881908e49e3ba478c35b4 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:14 p.m.