Triple

T26096306
Position Surface form Disambiguated ID Type / Status
Subject Uttar Pradesh Reorganisation Act, 2000 E658275 entity
Predicate reorganisedState P98498 FINISHED
Object Uttar Pradesh NE NERFINISHED

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: Uttar Pradesh | Statement: [Uttar Pradesh Reorganisation Act, 2000, reorganisedState, Uttar Pradesh]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reorganisedState
Context triple: [Uttar Pradesh Reorganisation Act, 2000, reorganisedState, Uttar Pradesh]
  • A. reorganizedAs
    Indicates that an existing entity has been restructured or reconfigured into a new organizational form or arrangement.
  • B. reorganizedIn
    Indicates that an entity underwent a structural or organizational change within a specified context, time, or framework.
  • C. reorganized
    Indicates that an entity has changed the structure, order, or arrangement of another entity or set of entities from a previous configuration.
  • D. reorganisedRegion chosen
    Indicates that a region has undergone a structural or administrative change, resulting in a new or altered regional configuration.
  • E. reorganizedFor
    Indicates that one entity has been rearranged, restructured, or otherwise modified in its organization for the benefit, use, or requirements of another entity.
  • 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_69ee5bbfc4d08190a1b206d0ac3a1e8d completed April 26, 2026, 6:38 p.m.
NER Named-entity recognition batch_69f612607c388190ab61d1ac7d18e08d completed May 2, 2026, 3:04 p.m.
PD Predicate disambiguation batch_69f611a9272881909093360472be832c completed May 2, 2026, 3 p.m.
Created at: April 26, 2026, 7:51 p.m.