Triple

T5518788
Position Surface form Disambiguated ID Type / Status
Subject Rajgarh, Madhya Pradesh E144751 entity
Predicate ISO3166-2code P42695 FINISHED
Object IN-MP E467478 NE FINISHED

How this triple was built (3 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: IN-MP | Statement: [Rajgarh, Madhya Pradesh, ISO3166-2code, IN-MP]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: IN-MP
Context triple: [Rajgarh, Madhya Pradesh, ISO3166-2code, IN-MP]
  • A. IN-MP chosen
    IN-MP is the ISO 3166-2 code that designates the Indian state of Madhya Pradesh.
  • B. IMP
    IMP is an early packet-switching node used in the ARPANET, serving as a precursor to modern internet routers.
  • C. IN-TR
    IN-TR is the ISO 3166-2 code that uniquely identifies the Indian state of Tripura.
  • D. IMB
    IMB was a large underground water Cherenkov detector in the United States, originally built to search for proton decay and later known for detecting neutrinos from supernova SN 1987A.
  • E. IN-HP
    IN-HP is the ISO 3166-2 code representing the Indian state of Himachal Pradesh.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ISO3166-2code
Context triple: [Rajgarh, Madhya Pradesh, ISO3166-2code, IN-MP]
  • A. ISO3166-2RegionCode chosen
    Indicates the standardized ISO 3166-2 code that specifies the particular primary administrative subdivision (such as a state, province, or region) to which an entity belongs.
  • B. ISO3166-2DifferentFrom
    Indicates that two ISO 3166-2 subdivision codes are explicitly distinct and should not be considered equivalent or interchangeable.
  • C. ISO3166-1Code
    Indicates the standardized two- or three-letter country or territory code assigned under the ISO 3166-1 international standard.
  • D. ISOCode
    Indicates that an entity is associated with a specific standardized code defined by the International Organization for Standardization (ISO).
  • E. ISO3166codePredecessorOf
    Indicates that one ISO 3166 country code served as the predecessor or was replaced by another ISO 3166 country code in the standard’s historical sequence.
  • F. None of above.

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_69c008f77ff88190b0cd50ca207295d1 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c01f6eb604819092e9b2207dc741a9 completed March 22, 2026, 4:57 p.m.
NED1 Entity disambiguation (via context triple) batch_69c027e57ed88190b2ff3245226851d1 completed March 22, 2026, 5:33 p.m.
PD Predicate disambiguation batch_69c01b0a06348190b39ac9fe80d2836a completed March 22, 2026, 4:38 p.m.
Created at: March 22, 2026, 3:33 p.m.