Triple

T4882149
Position Surface form Disambiguated ID Type / Status
Subject VAPR E109352 entity
Predicate denotes P129 FINISHED
Object Porbandar Airport E20129 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: Porbandar Airport | Statement: [VAPR, denotes, Porbandar Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Porbandar Airport
Context triple: [VAPR, denotes, 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. Rajkot Airport
    Rajkot Airport is a domestic airport serving the city of Rajkot and surrounding regions in the Indian state of Gujarat.
  • C. 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.
  • D. Kheria Airport
    Kheria Airport is a domestic and military airfield serving the city of Agra in Uttar Pradesh, India, located near the Taj Mahal and operated jointly by the Indian Air Force and civil aviation authorities.
  • E. Nal Airport
    Nal Airport is a domestic airport serving the city of Bikaner in the Indian state of Rajasthan.
  • 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_69bd440e9d64819083e82cf33b4d9570 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6dde6fcc8190a5aa7587f85632bd completed March 20, 2026, 3:55 p.m.
NED1 Entity disambiguation (via context triple) batch_69be81b60ea48190ae8cd7ef9c30a388 completed March 21, 2026, 11:32 a.m.
Created at: March 20, 2026, 1:27 p.m.