Triple

T115693
Position Surface form Disambiguated ID Type / Status
Subject Government of India Act 1919 E2332 entity
Predicate limitedPowersOf P99 FINISHED
Object central legislature 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: central legislature | Statement: [Government of India Act 1919, limitedPowersOf, central legislature]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: limitedPowersOf
Context triple: [Government of India Act 1919, limitedPowersOf, central legislature]
  • A. exclusivePower
    Indicates that one entity holds sole authority or control over another entity or a specific domain, excluding others from sharing that power.
  • B. hasLimitation chosen
    Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
  • C. limitsOffice
    Indicates that one entity imposes a restriction or cap on the scope, duration, or powers of another entity’s office or official position.
  • D. allows
    Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
  • E. grantedTo
    Indicates that a right, permission, or resource has been formally given or assigned by one party to another.
  • 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_69a2506c5428819085c28a8884790e29 completed Feb. 28, 2026, 2:18 a.m.
NER Named-entity recognition batch_69a257845c548190bfb49409988d1c57 completed Feb. 28, 2026, 2:48 a.m.
PD Predicate disambiguation batch_69a256456d908190b52c937fe6c4343f completed Feb. 28, 2026, 2:43 a.m.
Created at: Feb. 28, 2026, 2:24 a.m.