Triple
T2194790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warren Hastings |
E49945
|
entity |
| Predicate | impeachmentStart |
P13552
|
FINISHED |
| Object | 1788 |
—
|
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: 1788 | Statement: [Warren Hastings, impeachmentStart, 1788]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impeachmentStart Context triple: [Warren Hastings, impeachmentStart, 1788]
-
A.
impeached
Indicates that a formal charge of misconduct has been brought against a public official through an official legislative or judicial process.
-
B.
impeachmentYear
chosen
Indicates the year in which an entity (typically a public official) was formally impeached.
-
C.
canImpeach
Indicates that one entity has the authority or power to formally impeach another entity.
-
D.
impeachmentTarget
Indicates that an entity is the person or official against whom impeachment proceedings are directed.
-
E.
impeachmentGrounds
Indicates that a particular reason, action, or circumstance serves as a valid basis or justification for initiating impeachment proceedings against an officeholder.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf764e348190896af2aeb5520038 |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbda52328819089c7ab111bebb0ca |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.