Triple

T7761303
Position Surface form Disambiguated ID Type / Status
Subject Charlotte–Monroe Executive Airport E176026 entity
Predicate FAA LID P420 FINISHED
Object EQY E687968 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: EQY | Statement: [Charlotte–Monroe Executive Airport, FAA LID, EQY]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: EQY
Context triple: [Charlotte–Monroe Executive Airport, FAA LID, EQY]
  • A. EQY chosen
    EQY is the IATA airport code for Charlotte–Monroe Executive Airport, a public airport serving the Monroe and greater Charlotte area in North Carolina, United States.
  • B. EQE
    EQE is a fully electric executive sedan from Mercedes-Benz’s EQ lineup, positioned as a mid-size luxury alternative to the traditional E-Class.
  • C. EYKA
    EYKA is the ICAO airport code for Kaunas Airport, an international airport serving the city of Kaunas in Lithuania.
  • D. EQ
    EQ is Mercedes-Benz’s dedicated sub-brand for electric vehicles and related technologies, representing the company’s push into premium, battery-powered mobility.
  • E. EYD
    EYD is the commonly used abbreviation for "Ejaan Yang Disempurnakan," the standardized Indonesian spelling system officially adopted in Indonesia.
  • 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_69c69962923c8190ac74d28b4f9fe0a0 completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c704036c588190a441e56c738cc309 completed March 27, 2026, 10:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8d6c8276c8190bdc3efc2a6175610 completed March 29, 2026, 7:37 a.m.
Created at: March 27, 2026, 4:09 p.m.