Triple

T22143592
Position Surface form Disambiguated ID Type / Status
Subject Luton Airport terminal DART station E547227 entity
Predicate locatedIn P40 FINISHED
Object Luton 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: Luton | Statement: [Luton Airport terminal DART station, locatedIn, Luton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Luton
Context triple: [Luton Airport terminal DART station, locatedIn, Luton]
  • A. Luton chosen
    Luton is a large town in Bedfordshire, England, known for its international airport and diverse urban population.
  • B. Aylesbury
    Aylesbury is a historic market town in southern England that serves as an important commercial and administrative center in Buckinghamshire.
  • C. Hemel Hempstead
    Hemel Hempstead is a large town in southern England, known as a post-war New Town and major commercial and residential centre within Hertfordshire.
  • D. Hertford
    Hertford is a historic market town and the county town of Hertfordshire in southern England.
  • E. Hertford
    Hertford is a small historic town in northeastern North Carolina known for its riverside setting and traditional Southern charm.
  • 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_69e11e3a95d88190a3bd80d9471976c3 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f129c045448190b3d189cdb8c0d2fd completed April 28, 2026, 9:42 p.m.
Created at: April 16, 2026, 8:32 p.m.