Triple

T22833322
Position Surface form Disambiguated ID Type / Status
Subject EWB E565866 entity
Predicate hasIATACode P2569 FINISHED
Object EWB 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: EWB | Statement: [EWB, hasIATACode, EWB]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: EWB
Context triple: [EWB, hasIATACode, EWB]
  • A. EWB chosen
    EWB is the IATA airport code for New Bedford Regional Airport, a public airport serving New Bedford, Massachusetts.
  • B. EWEB
    EWEB is the public utility that provides water and electricity services to the Eugene, Oregon area.
  • C. EVB
    EVB (Edge Virtual Bridging) is an IEEE networking standard that defines mechanisms for managing and integrating virtualized network interfaces on edge switches and servers in data center environments.
  • D. EWI
    EWI is the abbreviation for the Faculty of Electrical Engineering, Mathematics and Computer Science at Delft University of Technology, known for its research and education in engineering and computational sciences.
  • E. EWI
    EWI is the Polish vehicle registration code assigned to the Wieluń area in the Łódź Voivodeship.
  • 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_69e24585ab1c81909b2b5065d15805d5 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17e2d830881908d69929b854aad66 completed April 29, 2026, 3:42 a.m.
Created at: April 17, 2026, 3:35 p.m.