Triple

T19291184
Position Surface form Disambiguated ID Type / Status
Subject Porbandar coast E482442 entity
Predicate transport P230 FINISHED
Object served by Porbandar 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: served by Porbandar Airport | Statement: [Porbandar coast, transport, served by Porbandar Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: served by Porbandar Airport
Context triple: [Porbandar coast, transport, served by Porbandar Airport]
  • A. Porbandar Airport chosen
    Porbandar Airport is a domestic airport in Gujarat, India, providing air connectivity to the coastal city of Porbandar and surrounding regions.
  • B. Bhavnagar airport
    Bhavnagar Airport is a domestic airport in Gujarat, India, serving the city of Bhavnagar and its surrounding region with scheduled commercial flights.
  • C. Rajkot Airport
    Rajkot Airport is a domestic airport serving the city of Rajkot and surrounding regions in the Indian state of Gujarat.
  • D. 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.
  • E. Kolhapur Airport
    Kolhapur Airport is a regional airport in Maharashtra, India, serving the city of Kolhapur and its surrounding areas with domestic air connectivity.
  • 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_69d8e8cf61b0819096fe3e4107827c4e completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e5fc05c9dc8190846b279f82ae0fa3 completed April 20, 2026, 10:12 a.m.
Created at: April 10, 2026, 1:31 p.m.