Triple
T5573915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 124 of the Constitution of India |
E146269
|
entity |
| Predicate | removalGroundsInclude |
P64524
|
FINISHED |
| Object | proved misbehaviour |
—
|
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: proved misbehaviour | Statement: [Article 124 of the Constitution of India, removalGroundsInclude, proved misbehaviour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: removalGroundsInclude Context triple: [Article 124 of the Constitution of India, removalGroundsInclude, proved misbehaviour]
-
A.
hasGrounds
Indicates that one entity possesses or includes a physical area of land or outdoor space associated with it.
-
B.
coversGrounds
Indicates that one entity extends over, occupies, or lies across the surface area of another entity (typically land or grounds).
-
C.
mayRemove
Indicates that one entity is permitted or authorized to remove another entity or its association.
-
D.
excludedFrom
Indicates that one entity is deliberately not included within the scope, membership, or applicability of another entity or set.
-
E.
exclusionBasis
Indicates the reason or criterion used to exclude an entity from a set, process, or consideration.
- F. None of above. chosen
Provenance (4 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_69c008ffed108190a084602227af6157 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02054ce8c819093e1a6379ec92006 |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b147cc081909237f3f2967d4cb8 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0684908190ae2d14f0bd2ab892 |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:37 p.m.