Triple
T22077682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | President's Rule |
E545561
|
entity |
| Predicate | misuseConcern |
P17598
|
FINISHED |
| Object | allegations of partisan use by Union government |
—
|
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: allegations of partisan use by Union government | Statement: [President's Rule, misuseConcern, allegations of partisan use by Union government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: misuseConcern Context triple: [President's Rule, misuseConcern, allegations of partisan use by Union government]
-
A.
misuseCanConstitute
Indicates that improper or incorrect use of something can amount to, or be considered as, a particular offense, violation, or condition.
-
B.
concern
Indicates that one entity is about, relates to, or is of interest or importance to another entity.
-
C.
raisedConcernAbout
chosen
Indicates that one entity has expressed worry, doubt, or objection regarding another entity or issue.
-
D.
concernsClause
Indicates that one entity (such as a document, statement, or discussion) is about, relates to, or addresses a particular clause.
-
E.
allegedUse
Indicates that something is claimed or suspected to have been used, without confirming that the use actually occurred.
- 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_69e11e3523488190badd54b5d580c00d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128b38844819084526372fa6c6e35 |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:28 p.m.