Triple

T17343372
Position Surface form Disambiguated ID Type / Status
Subject Runway 26R at Paris Charles de Gaulle Airport E421119 entity
Predicate icaoAirportCode P419 FINISHED
Object LFPG E10903 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: LFPG | Statement: [Runway 26R at Paris Charles de Gaulle Airport, icaoAirportCode, LFPG]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: LFPG
Context triple: [Runway 26R at Paris Charles de Gaulle Airport, icaoAirportCode, LFPG]
  • A. LFPG chosen
    LFPG is the ICAO airport code for Paris Charles de Gaulle Airport, France’s largest and busiest international air hub.
  • B. PFG
    PFG is the stock ticker symbol for Principal Financial Group, a U.S.-based global financial services and investment management company.
  • C. LF
    LF is the commonly used abbreviation for the Linux Foundation, a nonprofit organization that supports and promotes the development of the Linux kernel and other open-source software projects.
  • D. LF
    LF is a German vehicle registration code assigned to the Traunstein district in the state of Bavaria.
  • E. LPFR
    LPFR is the ICAO airport code for Faro Airport, the main international gateway to Portugal’s Algarve region.
  • 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_69d889d3adc881909319f1edb8d2a956 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43a18aca88190a816da85dd5fe371 completed April 19, 2026, 2:12 a.m.
NED1 Entity disambiguation (via context triple) batch_6a018c5a7c308190b478918b66a4276c completed May 11, 2026, 7:59 a.m.
Created at: April 10, 2026, 5:44 a.m.