Triple
T12656573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Revision |
E302298
|
entity |
| Predicate | rejectionReason |
P6667
|
FINISHED |
| Object | concern over mixing judicial and executive powers |
—
|
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: concern over mixing judicial and executive powers | Statement: [Council of Revision, rejectionReason, concern over mixing judicial and executive powers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rejectionReason Context triple: [Council of Revision, rejectionReason, concern over mixing judicial and executive powers]
-
A.
reasonForDecline
chosen
Indicates the explanation or cause given for why something was rejected, reduced, or not accepted.
-
B.
rejectedBecause
Indicates that one entity refused, dismissed, or did not accept another entity specifically due to a stated reason or cause.
-
C.
resultOfRejection
Indicates that something occurs as a consequence or outcome of a prior act of rejection.
-
D.
rejectedBy
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
E.
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.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b78ce8819091f15dd5013e6da5 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:18 p.m.