Triple

T180794
Position Surface form Disambiguated ID Type / Status
Subject Manchester Airport E3870 entity
Predicate hasICAOcode P419 FINISHED
Object EGCC E3871 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: EGCC | Statement: [Manchester Airport, hasICAOcode, EGCC]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: EGCC
Context triple: [Manchester Airport, hasICAOcode, EGCC]
  • A. EGCC chosen
    EGCC is the ICAO airport code for Manchester Airport, a major international airport in Greater Manchester, England.
  • B. AGSU
    AGSU is the modern U.S. Army service uniform inspired by the World War II-era "pinks and greens" style, worn for everyday professional and ceremonial duties.
  • C. ECA
    The Economic Cooperation Administration (ECA) was the U.S. government agency responsible for administering the Marshall Plan to aid European economic recovery after World War II.
  • D. ECA
    ECA is a regional United Nations commission focused on promoting economic and social development across the African continent.
  • E. ECU
    ECU is the three-letter ISO 3166-1 alpha-3 country code that uniquely identifies Ecuador in international standards and data systems.
  • 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_69a25497e2f08190a040f8c6e1842643 completed Feb. 28, 2026, 2:36 a.m.
NER Named-entity recognition batch_69a25bafd5808190a0a0cb2b21ce007f completed Feb. 28, 2026, 3:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69a2f0b71080819086362f6036b41162 completed Feb. 28, 2026, 1:42 p.m.
Created at: Feb. 28, 2026, 2:40 a.m.