Triple

T38030247
Position Surface form Disambiguated ID Type / Status
Subject Dausa Lok Sabha constituency E948887 entity
Predicate previouslyIncludedDistrict P110170 FINISHED
Object Jaipur district 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: Jaipur district | Statement: [Dausa Lok Sabha constituency, previouslyIncludedDistrict, Jaipur district]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: previouslyIncludedDistrict
Context triple: [Dausa Lok Sabha constituency, previouslyIncludedDistrict, Jaipur district]
  • A. oneOfOriginalDistricts
    Indicates that an entity belongs to, or is included among, the original set of districts defined for a given area or jurisdiction.
  • B. formerDistrict
    Indicates that one entity previously served as a district of another entity but no longer holds that status.
  • C. electoralDistrictIncludes
    Indicates that a given electoral district geographically contains or encompasses a specified area or location.
  • D. includesDistrict
    Indicates that one administrative or geographic entity contains or encompasses a specific district within its boundaries.
  • E. formerlyInDistrict chosen
    Indicates that an entity was once located in or part of a particular district, but is no longer within that district.
  • 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_69f76efd1bc48190a729097fe5177b61 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_6a00037bf4148190a58593d30efdd3f8 completed May 10, 2026, 4:03 a.m.
PD Predicate disambiguation batch_6a0000b7af608190b718fc4111bcdad8 completed May 10, 2026, 3:51 a.m.
Created at: May 3, 2026, 4:20 p.m.