Triple

T7241150
Position Surface form Disambiguated ID Type / Status
Subject Bhopal E155357 entity
Predicate hasAirport P105 FINISHED
Object Raja Bhoj Airport E107037 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: Raja Bhoj Airport | Statement: [Bhopal, hasAirport, Raja Bhoj Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Raja Bhoj Airport
Context triple: [Bhopal, hasAirport, Raja Bhoj Airport]
  • A. Raja Bhoj Airport chosen
    Raja Bhoj Airport is the main domestic and international airport serving Bhopal and the surrounding region in the Indian state of Madhya Pradesh.
  • B. Devi Ahilya Bai Holkar Airport
    Devi Ahilya Bai Holkar Airport is the main domestic and international airport serving Indore and the surrounding region in the Indian state of Madhya Pradesh.
  • C. Khajuraho Airport
    Khajuraho Airport is a domestic airport in Madhya Pradesh, India, serving the town of Khajuraho and its famous UNESCO-listed temple complex.
  • D. Jabalpur Airport
    Jabalpur Airport is a domestic airport in Madhya Pradesh, India, serving the city of Jabalpur and its surrounding region.
  • E. Nagpur Airport
    Nagpur Airport is a major international airport in Nagpur, Maharashtra, serving as a key aviation hub for central India.
  • 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_69c688143bfc81908d4176617735e601 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6ea39230481908401ead83d8666cd completed March 27, 2026, 8:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7cc4292c881909ca7b140a83ed53d completed March 28, 2026, 12:40 p.m.
Created at: March 27, 2026, 2:55 p.m.