Triple

T12541010
Position Surface form Disambiguated ID Type / Status
Subject Rajahmundry Airport E299836 entity
Predicate IATAcode P418 FINISHED
Object RJA E143160 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: RJA | Statement: [Rajahmundry Airport, IATAcode, RJA]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RJA
Context triple: [Rajahmundry Airport, IATAcode, RJA]
  • A. RJA chosen
    RJA is the ICAO airline designator used for Royal Jordanian, the flag carrier airline of Jordan.
  • B. RJAA
    RJAA is the ICAO airport code for Narita International Airport, a major international gateway serving the Tokyo metropolitan area in Japan.
  • C. RJAF
    RJAF is the acronym for the Royal Jordanian Air Force, the aerial warfare branch of Jordan’s armed forces.
  • D. RJKA
    RJKA is the ICAO airport code for Amami Airport, a regional airport serving Amami Ōshima in Kagoshima Prefecture, Japan.
  • E. RJAH
    RJAH is the ICAO airport code for Hyakuri Air Base, a Japanese military airfield in Ibaraki Prefecture.
  • 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_69d6ada707008190aaec1238117c9379 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d9546fc620819093335988dbab3256 completed April 10, 2026, 7:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6557cb180819083ee10708320199e completed May 2, 2026, 7:50 p.m.
Created at: April 8, 2026, 9:57 p.m.