Triple

T3511849
Position Surface form Disambiguated ID Type / Status
Subject Rajkot Airport E74212 entity
Predicate locatedIn P40 FINISHED
Object Rajkot E24131 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 | Statement: [Rajkot Airport, locatedIn, Rajkot]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rajkot
Context triple: [Rajkot Airport, locatedIn, Rajkot]
  • A. Rajkot chosen
    Rajkot is a major city in the Indian state of Gujarat, known as an important commercial and cultural center of the Saurashtra region.
  • B. Bhuj
    Bhuj is a historic city in the Kutch district of Gujarat, India, known for its rich cultural heritage, traditional handicrafts, and role as a regional commercial and administrative center.
  • C. Bhavnagar
    Bhavnagar is a coastal city in western India known for its historic trading port, diamond cutting industry, and cultural heritage within the state of Gujarat.
  • D. Veraval
    Veraval is a coastal city in the Indian state of Gujarat, known historically as a major fishing and port town near the pilgrimage center of Somnath.
  • E. Vadodara
    Vadodara is a major city in western India known for its rich cultural heritage, educational institutions, and industrial development.
  • 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_69ad85cfb5c881909c9a2edd9d6043cc completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adbc10b6b48190bedfed6d34afc425 completed March 8, 2026, 6:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69b54c2144708190a4a620222eeee5d3 completed March 14, 2026, 11:53 a.m.
Created at: March 8, 2026, 3:19 p.m.