Triple

T21420133
Position Surface form Disambiguated ID Type / Status
Subject Trenton–Mercer Airport E528412 entity
Predicate ICAO code P419 FINISHED
Object KTTN 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: KTTN | Statement: [Trenton–Mercer Airport, ICAO code, KTTN]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: KTTN
Context triple: [Trenton–Mercer Airport, ICAO code, KTTN]
  • A. KTTN chosen
    KTTN is the ICAO airport code for Trenton–Mercer Airport, a public airport serving the Trenton, New Jersey area.
  • B. KTTA
    KTTA is the ICAO airport code for Raleigh Executive Jetport, a public general aviation airport serving the Raleigh, North Carolina area.
  • C. KTTD
    KTTD is the ICAO airport code for Troutdale Airport, a public general aviation airport serving the Troutdale area near Portland, Oregon.
  • D. KTT
    KTT is a Polish vehicle registration code assigned to the Tatra County (powiat tatrzański) region in the Lesser Poland Voivodeship.
  • E. KTT
    KTT is the London borough code used to identify the Royal Borough of Kingston upon Thames.
  • 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_69e0c454c248819093425d1099101c09 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e8b2cdb40481909542f2c953bbab64 completed April 22, 2026, 11:36 a.m.
Created at: April 16, 2026, 5:47 p.m.