Triple

T24118330
Position Surface form Disambiguated ID Type / Status
Subject Seventy-third Amendment to the Constitution of India E597580 entity
Predicate addedSchedule P144803 FINISHED
Object Eleventh Schedule of the Constitution of India 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: Eleventh Schedule of the Constitution of India | Statement: [Seventy-third Amendment to the Constitution of India, addedSchedule, Eleventh Schedule of the Constitution of India]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: addedSchedule
Context triple: [Seventy-third Amendment to the Constitution of India, addedSchedule, Eleventh Schedule of the Constitution of India]
  • A. insertedSchedule chosen
    Indicates that one entity has added or placed a schedule into another entity or system.
  • B. scheduledAs
    Indicates that one entity is assigned or arranged to occur or function in the role, time, or capacity specified by another entity within a schedule.
  • C. definesScheduleFor
    Indicates that one entity establishes or specifies the schedule according to which another entity operates or is organized.
  • D. scheduleUS
    Indicates that an entity arranges or assigns a time for something specifically within the context of the United States.
  • E. scheduledDuring
    Indicates that one event or activity is planned to occur within the time interval defined by another event or period.
  • 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_69e288c74200819098ab875b592cb39f completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1dee091c48190a55d36f28c332749 completed April 29, 2026, 10:35 a.m.
PD Predicate disambiguation batch_69f17651458c8190bbfd301883e46085 completed April 29, 2026, 3:09 a.m.
Created at: April 17, 2026, 11:05 p.m.