Triple

T923821
Position Surface form Disambiguated ID Type / Status
Subject Constituent Assembly of India E19938 entity
Predicate cameIntoForceOfConstitutionDate P762 FINISHED
Object 1950-01-26 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: 1950-01-26 | Statement: [Constituent Assembly of India, cameIntoForceOfConstitutionDate, 1950-01-26]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: cameIntoForceOfConstitutionDate
Context triple: [Constituent Assembly of India, cameIntoForceOfConstitutionDate, 1950-01-26]
  • A. cameIntoForceInYear
    Indicates that a law, agreement, or formal measure became legally effective or operational in a specified calendar year.
  • B. dateOfEnactment
    Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
  • C. constitutionEffectiveFrom chosen
    Indicates the date or point in time from which a particular constitution or constitutional provision is legally in force and applicable.
  • D. dateOfPromulgation
    Indicates the date on which a law, decree, or official act is formally proclaimed and put into effect.
  • E. dateEnacted
    Indicates the date on which a law, policy, or formal measure was officially put into effect or became legally operative.
  • 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_69a493a099788190a696d9d8408cbaf4 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b3296f50819087f809fbe90b139e completed March 1, 2026, 9:44 p.m.
PD Predicate disambiguation batch_69a4b295b02481908e5f53bfcb83cc94 completed March 1, 2026, 9:41 p.m.
Created at: March 1, 2026, 7:40 p.m.