Triple
T3421773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Counter-Remonstrants |
E72129
|
entity |
| Predicate | rejectedDoctrine |
P5486
|
FINISHED |
| Object | conditional election |
—
|
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: conditional election | Statement: [Counter-Remonstrants, rejectedDoctrine, conditional election]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rejectedDoctrine Context triple: [Counter-Remonstrants, rejectedDoctrine, conditional election]
-
A.
deniesDoctrine
chosen
Indicates that one entity rejects, opposes, or refuses to accept the truth or validity of a particular doctrine associated with another entity.
-
B.
rejectedBy
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
C.
rejectedBecause
Indicates that one entity refused, dismissed, or did not accept another entity specifically due to a stated reason or cause.
-
D.
rejectedJustification
Indicates that a proposed justification or reason offered in a context (e.g., argument, decision, or claim) has been evaluated and not accepted as valid or sufficient.
-
E.
rejectedAward
Indicates that an entity refused to accept or declined an award that was offered or granted to it.
- 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb950f65481908c4aad15516e7a7c |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.