Triple
T2324146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illinois General Assembly |
E48247
|
entity |
| Predicate | senateImpeachmentRole |
P2841
|
FINISHED |
| Object | tries impeachments |
—
|
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: tries impeachments | Statement: [Illinois General Assembly, senateImpeachmentRole, tries impeachments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: senateImpeachmentRole Context triple: [Illinois General Assembly, senateImpeachmentRole, tries impeachments]
-
A.
impeachmentRole
chosen
Indicates the specific role or capacity an entity holds in relation to an impeachment process or proceeding.
-
B.
canImpeach
Indicates that one entity has the authority or power to formally impeach another entity.
-
C.
impeachmentTarget
Indicates that an entity is the person or official against whom impeachment proceedings are directed.
-
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.
legislativeRole
Indicates that an entity holds or performs a specific official position, function, or duty within a legislative body or lawmaking process.
- 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_69a88aa308a88190b0b86c011fda7fce |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc5909cc48190aab257313542dc49 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.