Triple

T13804332
Position Surface form Disambiguated ID Type / Status
Subject Kheria Airport E331721 entity
Predicate hasIATACode P2569 FINISHED
Object AGR E329571 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: AGR | Statement: [Kheria Airport, hasIATACode, AGR]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: AGR
Context triple: [Kheria Airport, hasIATACode, AGR]
  • A. AGR chosen
    AGR is the IATA airport code for Agra Airport, which serves the city of Agra in India near the Taj Mahal.
  • B. AGR
    AGR is a United Nations treaty that defines and coordinates the network of major international road routes across Europe.
  • C. AGR
    AGR is the commonly used abbreviation for the U.S. military’s Active Guard and Reserve program, which places Reserve Component members on full-time active duty to support and administer reserve units.
  • D. AG
    AG is an Indonesian vehicle registration code used for motor vehicles registered in certain regions of East Java, including Trenggalek.
  • E. AG
    AG is the two-letter ISO 3166-1 alpha-2 country code assigned to Antigua and Barbuda.
  • 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_69d81c59f8808190a851bc56afdc55e9 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de026c36108190a7436034a730a261 completed April 14, 2026, 9:01 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7b08db39c8190a76637b36b77d643 completed May 3, 2026, 8:31 p.m.
Created at: April 9, 2026, 10:12 p.m.