Triple

T25687032
Position Surface form Disambiguated ID Type / Status
Subject Indian Penal Code E644091 entity
Predicate replacedByInJammuAndKashmir P163030 FINISHED
Object Ranbir Penal Code (historically) 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: Ranbir Penal Code (historically) | Statement: [Indian Penal Code, replacedByInJammuAndKashmir, Ranbir Penal Code (historically)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: replacedByInJammuAndKashmir
Context triple: [Indian Penal Code, replacedByInJammuAndKashmir, Ranbir Penal Code (historically)]
  • A. replacedByAsCapitalOfBritishIndia
    Indicates that one entity ceased to be the capital of British India and was succeeded in that role by another entity.
  • B. replacedByInDaman
    Indicates that something has been superseded or substituted by another entity specifically within the context or jurisdiction of Daman.
  • C. placedBy
    Indicates that one entity was positioned, set, or put in a location or context by another entity.
  • D. wasUnionTerritoryAs
    Indicates that an entity held the status of a union territory during a specified time or under specified conditions.
  • E. namedJunagarhSince
    Indicates that an entity has held the name "Junagarh" starting from a specified point in time.
  • F. None of above. chosen

Provenance (4 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_69e77e8046888190b07ffa58c7e2c37a completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f63639a84c81909d700a539b458b42 completed May 2, 2026, 5:36 p.m.
PD Predicate disambiguation batch_69f63182f1408190bddc1214fcbd6145 completed May 2, 2026, 5:16 p.m.
PDg Predicate description generation batch_69f6352df6148190bc10772cd40bd7b3 completed May 2, 2026, 5:32 p.m.
Created at: April 21, 2026, 8:10 p.m.