Triple

T3453574
Position Surface form Disambiguated ID Type / Status
Subject IN-HP E72848 entity
Predicate registry P86 FINISHED
Object ISO 3166-2:IN E100868 NE 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: ISO 3166-2:IN | Statement: [IN-HP, registry, ISO 3166-2:IN]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: ISO 3166-2:IN
Context triple: [IN-HP, registry, ISO 3166-2:IN]
  • A. ISO 3166-2:IN chosen
    ISO 3166-2:IN is the section of the ISO 3166 standard that defines internationally recognized subdivision codes for the states and union territories of India.
  • B. ISO 3166-2:PK
    ISO 3166-2:PK is the section of the ISO 3166-2 standard that defines the official subdivision codes for the provinces and territories of Pakistan.
  • C. ISO 3166-2:PR
    ISO 3166-2:PR is the subdivision code entry in the ISO 3166-2 standard that defines the territorial code for Puerto Rico.
  • D. ISO 3166-2:MP
    ISO 3166-2:MP is the ISO 3166-2 entry that defines the subdivision codes for the Northern Mariana Islands, a U.S. commonwealth in the Pacific Ocean.
  • E. Estado da Índia
    Estado da Índia was the Portuguese Empire’s colonial state in Asia, encompassing its key trading ports and territories from the early 16th century onward.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ad85b12a908190a1d10a6b03b4f8ae completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adbaa457fc8190824ca00254e962f9 completed March 8, 2026, 6:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69b360fc823c8190a0f1807b39706b3f completed March 13, 2026, 12:57 a.m.
Created at: March 8, 2026, 3:16 p.m.