Triple

T21620176
Position Surface form Disambiguated ID Type / Status
Subject Constitution (Forty-second Amendment) Act, 1976 E533554 entity
Predicate attemptedToLimit P28788 FINISHED
Object Judicial review 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: Judicial review | Statement: [Constitution (Forty-second Amendment) Act, 1976, attemptedToLimit, Judicial review]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: attemptedToLimit
Context triple: [Constitution (Forty-second Amendment) Act, 1976, attemptedToLimit, Judicial review]
  • A. aimedToLimit chosen
    Indicates an action or policy that was intentionally directed toward restricting, reducing, or constraining something.
  • B. attemptLimit
    Indicates a restriction on how many times an action or operation may be attempted before it is stopped or blocked.
  • C. oversLimit
    Indicates that an entity exceeds a specified limit, threshold, or allowed maximum.
  • D. isLimitOf
    Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
  • E. hasLimitation
    Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
  • 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_69e0c464fba881908d0ff2ac80511ce1 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef3baeeae48190b78583b3bec8ee33 completed April 27, 2026, 10:34 a.m.
PD Predicate disambiguation batch_69e69665fe8c8190af7e38785db188b2 completed April 20, 2026, 9:11 p.m.
Created at: April 16, 2026, 6:34 p.m.