Triple

T18860928
Position Surface form Disambiguated ID Type / Status
Subject Vadodara Junction E461307 entity
Predicate hasNearbyAirport P4363 FINISHED
Object Vadodara Airport 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: Vadodara Airport | Statement: [Vadodara Junction, hasNearbyAirport, Vadodara Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vadodara Airport
Context triple: [Vadodara Junction, hasNearbyAirport, Vadodara Airport]
  • A. Vadodara Airport chosen
    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.
  • B. Surat Airport
    Surat Airport is a domestic and international airport serving the city of Surat in the Indian state of Gujarat.
  • C. Rajkot Airport
    Rajkot Airport is a domestic airport serving the city of Rajkot and surrounding regions in the Indian state of Gujarat.
  • D. Bhavnagar airport
    Bhavnagar Airport is a domestic airport in Gujarat, India, serving the city of Bhavnagar and its surrounding region with scheduled commercial flights.
  • E. Nashik Airport
    Nashik Airport is a regional airport serving the city of Nashik in Maharashtra, India, handling domestic flights and supporting both civilian and defense aviation activities.
  • 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_69d8dcfb7b9c8190854e7b171b98ea2e completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c060bfc4819092ac591692a6ccd5 completed April 20, 2026, 5:57 a.m.
Created at: April 10, 2026, 11:57 a.m.