Triple

T19057193
Position Surface form Disambiguated ID Type / Status
Subject Talagi Airport E466429 entity
Predicate IATAcode P418 FINISHED
Object ARH 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: ARH | Statement: [Talagi Airport, IATAcode, ARH]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ARH
Context triple: [Talagi Airport, IATAcode, ARH]
  • A. ARH chosen
    ARH is the IATA airport code for Arkhangelsk Talagi Airport, a regional airport serving the city of Arkhangelsk in northwestern Russia.
  • B. ARHA
    ARHA is the post-nominal title used to denote an Associate member of the Royal Hibernian Academy, an Irish institution dedicated to the promotion of the visual arts.
  • C. ARLH
    ARLH is the abbreviation for the Alabama Register of Landmarks and Heritage, a state-level list recognizing historically and culturally significant sites in Alabama.
  • D. ARL
    ARL (Australian Rugby League) was the top-level rugby league competition in Australia during the mid-1990s, preceding the formation of the National Rugby League (NRL).
  • E. ARL
    ARL is the airport rail link service connecting central Bangkok with Suvarnabhumi International Airport.
  • 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_69d8dd040fb881909af2a964f65ad208 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5dc067f788190b3b149dfee370435 completed April 20, 2026, 7:55 a.m.
Created at: April 10, 2026, 12:03 p.m.