Triple
T19734907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indore district |
E473952
|
entity |
| Predicate | ISOCode |
P208
|
FINISHED |
| Object | IN-MP |
—
|
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: IN-MP | Statement: [Indore district, ISOCode, IN-MP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IN-MP Context triple: [Indore district, ISOCode, IN-MP]
-
A.
IN-MP
chosen
IN-MP is the ISO 3166-2 code that designates the Indian state of Madhya Pradesh.
-
B.
INM
INM is Mexico’s federal agency responsible for regulating and overseeing immigration, border control, and the legal status of foreign nationals in the country.
-
C.
IMP
IMP is an early packet-switching node used in the ARPANET, serving as a precursor to modern internet routers.
-
D.
IN-TR
IN-TR is the ISO 3166-2 code that uniquely identifies the Indian state of Tripura.
-
E.
IN-UP
IN-UP is the ISO 3166-2 code that designates the Indian state of Uttar Pradesh.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6515d138c8190a4c4d112ed5756a3 |
completed | April 20, 2026, 4:16 p.m. |
Created at: April 10, 2026, 1:47 p.m.