Triple

T522346
Position Surface form Disambiguated ID Type / Status
Subject Terminal 3 (Manchester Airport) E10844 entity
Predicate hasIATACode P2569 FINISHED
Object MAN E3870 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: MAN | Statement: [Terminal 3 (Manchester Airport), hasIATACode, MAN]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MAN
Context triple: [Terminal 3 (Manchester Airport), hasIATACode, MAN]
  • A. MAN chosen
    MAN is the three-letter IATA airport code for Manchester Airport, a major international airport serving the Greater Manchester area in England.
  • B. MAN
    MAN is a German commercial vehicle and engineering company best known for manufacturing trucks, buses, and diesel engines.
  • C. Mann
    Mann is a common German surname borne by numerous notable figures in literature, politics, and the arts.
  • D. Manf
    Manf is the Arabic name for the ancient Egyptian city of Memphis, a historically significant capital near modern-day Cairo.
  • E. Male
    Male is the capital and most populous city of the Maldives, located on the southern edge of North Malé Atoll in the Indian Ocean.
  • 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_69a2e84b16c4819088d284c47c3a7968 completed Feb. 28, 2026, 1:06 p.m.
NER Named-entity recognition batch_69a2f1b372408190b3918fec45444674 completed Feb. 28, 2026, 1:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69a4ab1f95cc8190a6e2dfc3636110b5 completed March 1, 2026, 9:09 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.