Triple

T14277699
Position Surface form Disambiguated ID Type / Status
Subject Shamshabad E353956 entity
Predicate airportICAO P419 FINISHED
Object VOHS E349873 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: VOHS | Statement: [Shamshabad, airportICAO, VOHS]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: VOHS
Context triple: [Shamshabad, airportICAO, VOHS]
  • A. VOHS chosen
    VOHS is the ICAO airport code for Rajiv Gandhi International Airport serving Hyderabad, India.
  • B. VOH
    VOH is the vehicle registration code used on license plates for the district of Neustadt an der Waldnaab in Bavaria, Germany.
  • C. VOG
    VOG is the IATA airport code for Volgograd International Airport, a regional air transport hub serving the city of Volgograd in Russia.
  • D. VOCI
    VOCI is the ICAO airport code for Cochin International Airport in Kochi, India, a major international gateway in the state of Kerala.
  • E. VOHY
    VOHY is the ICAO airport code for Begumpet Airport, the former international airport serving Hyderabad, India.
  • 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_69d8278d25148190abf1a8c8f5f533ad completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de6583f0ec81909ebfc7a2c6351ff8 completed April 14, 2026, 4:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd326f62b4819084b1e984678991ae completed May 8, 2026, 12:46 a.m.
Created at: April 10, 2026, 1:10 a.m.