Triple

T20130010
Position Surface form Disambiguated ID Type / Status
Subject Bhopal–Indore road E490863 entity
Predicate startPoint P389 FINISHED
Object Bhopal 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: Bhopal | Statement: [Bhopal–Indore road, startPoint, Bhopal]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bhopal
Context triple: [Bhopal–Indore road, startPoint, Bhopal]
  • A. Bhopal chosen
    Bhopal is the capital city of the Indian state of Madhya Pradesh, known for its historic lakes, administrative importance, and the site of the 1984 industrial disaster.
  • B. Indore
    Indore is a major commercial and educational hub in central India, known for its vibrant markets, food culture, and rapidly growing urban infrastructure.
  • C. Bhilai
    Bhilai is an industrial city in central India best known for its large steel plant and planned urban infrastructure.
  • D. Jabalpur
    Jabalpur is a major city in the central Indian state of Madhya Pradesh, known for its industrial base, educational institutions, and nearby marble rock formations along the Narmada River.
  • E. Gwalior
    Gwalior is a historic city in the Indian state of Madhya Pradesh, renowned for its hilltop fort, rich royal heritage, and cultural significance.
  • 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_69da62651a0c8190a3e05e95e056a66b completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e66760b8f08190a66fbb2e9e3925a3 completed April 20, 2026, 5:50 p.m.
Created at: April 11, 2026, 11:31 p.m.