Triple

T14724658
Position Surface form Disambiguated ID Type / Status
Subject HEF Airport E345906 entity
Predicate IATAcode P418 FINISHED
Object HEF E330566 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: HEF | Statement: [HEF Airport, IATAcode, HEF]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: HEF
Context triple: [HEF Airport, IATAcode, HEF]
  • A. HEF chosen
    HEF is the FAA location identifier for Manassas Regional Airport in Virginia, a public airport serving general aviation and regional air traffic.
  • B. HEF
    HEF is the German vehicle registration code assigned to the district of Hersfeld-Rotenburg, centered around the town of Bad Hersfeld in Hesse.
  • C. HAF
    HAF is the commonly used abbreviation for the Hellenic Air Force, the air warfare branch of Greece’s armed forces.
  • D. HE
    HE is the Faculty of Health at Aarhus University, responsible for education and research in medical and health sciences.
  • E. HEE
    HEE is the acronym for Health Education England, the national body responsible for overseeing education, training, and workforce development for healthcare staff in England.
  • 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_69d822e5911c8190ba589f957dbd9ba7 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec25e9a14819081fa06fc601f295d completed April 14, 2026, 10:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69fdf09791e081908a1262717fd31445 completed May 8, 2026, 2:17 p.m.
Created at: April 10, 2026, 1:29 a.m.