Triple
T21175367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine Senate |
E521796
|
entity |
| Predicate | canImpeachOrTry |
P2449
|
FINISHED |
| Object | certain state officials |
—
|
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: certain state officials | Statement: [Maine Senate, canImpeachOrTry, certain state officials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canImpeachOrTry Context triple: [Maine Senate, canImpeachOrTry, certain state officials]
-
A.
canImpeach
chosen
Indicates that one entity has the authority or power to formally impeach another entity.
-
B.
impeachmentPossible
Indicates that formal removal proceedings can legitimately be initiated against a public official based on alleged misconduct or qualifying grounds.
-
C.
impeachmentInitiation
Indicates the formal start of a process to charge and potentially remove a public official from office for alleged misconduct.
-
D.
impeachmentGrounds
Indicates that a particular reason, action, or circumstance serves as a valid basis or justification for initiating impeachment proceedings against an officeholder.
-
E.
impeachmentTarget
Indicates that an entity is the person or official against whom impeachment proceedings are directed.
- 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_69e0b50e30748190b186824a206d39b9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7271597288190b04baff9ca8d866c |
completed | April 21, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3 p.m.