Triple
T28576284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weldon Amendment |
E723248
|
entity |
| Predicate | basisOfRefusal |
P23142
|
FINISHED |
| Object | moral objections |
—
|
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: moral objections | Statement: [Weldon Amendment, basisOfRefusal, moral objections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basisOfRefusal Context triple: [Weldon Amendment, basisOfRefusal, moral objections]
-
A.
rejectedBecause
Indicates that one entity refused, dismissed, or did not accept another entity specifically due to a stated reason or cause.
-
B.
rejectedBy
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
C.
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.
-
D.
reasonForDecline
Indicates the explanation or cause given for why something was rejected, reduced, or not accepted.
-
E.
decisionBasis
chosen
Indicates the underlying reason, criterion, or rationale on which a decision is made.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f650c7d5ac81908b1764972e438168 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 4:12 a.m.