Triple

T11133711
Position Surface form Disambiguated ID Type / Status
Subject Van Nuys Airport E263353 entity
Predicate FAAIdentifier P420 FINISHED
Object VNY E192949 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: VNY | Statement: [Van Nuys Airport, FAAIdentifier, VNY]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: VNY
Context triple: [Van Nuys Airport, FAAIdentifier, VNY]
  • A. VNY chosen
    VNY is the IATA code for Van Nuys Airport, a major general aviation airport located in the San Fernando Valley area of Los Angeles, California.
  • B. N.D.N.Y.
    N.D.N.Y. is the standard abbreviation for the United States District Court for the Northern District of New York, a federal trial court within the Second Circuit.
  • C. NYSA
    NYSA is the commonly used abbreviation for the New York State Archives, the official repository for New York State government records and historical documents.
  • D. LNY
    LNY is the IATA airport code for Lānaʻi Airport, the primary air gateway to the Hawaiian island of Lānaʻi.
  • E. NYL
    NYL is the FAA location identifier for Yuma International Airport in Yuma, Arizona.
  • 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_69d6aa9c0ba08190bbd19c217489b755 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8347a248190837e8c26f25f553a completed April 9, 2026, 5:56 p.m.
NED1 Entity disambiguation (via context triple) batch_69e46308d2f481908827d0d569802f89 completed April 19, 2026, 5:07 a.m.
Created at: April 8, 2026, 9:28 p.m.