Triple

T1089637
Position Surface form Disambiguated ID Type / Status
Subject Rajkot E24131 entity
Predicate hasTransport P1298 FINISHED
Object Rajkot Airport E74212 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: Rajkot Airport | Statement: [Rajkot, hasTransport, Rajkot Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rajkot Airport
Context triple: [Rajkot, hasTransport, Rajkot Airport]
  • A. Rajkot Airport chosen
    Rajkot Airport is a domestic airport serving the city of Rajkot and surrounding regions in the Indian state of Gujarat.
  • B. Vadodara Airport
    Vadodara Airport is a domestic airport in the city of Vadodara, India, serving as one of the key air transport hubs in the state of Gujarat.
  • C. Porbandar Airport
    Porbandar Airport is a domestic airport in Gujarat, India, providing air connectivity to the coastal city of Porbandar and surrounding regions.
  • D. Surat Airport
    Surat Airport is a domestic and international airport serving the city of Surat in the Indian state of Gujarat.
  • E. 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.
  • 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_69a49404428c819092dcc9632f5f7b8b completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4b97f216881909e9b8943ce2078e4 completed March 1, 2026, 10:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac599e543c8190bbb0558379d8d9d5 completed March 7, 2026, 5 p.m.
Created at: March 1, 2026, 7:42 p.m.