Triple

T17105822
Position Surface form Disambiguated ID Type / Status
Subject Kingsbury E415096 entity
Predicate adjacentTo P224 FINISHED
Object Neasden 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: Neasden | Statement: [Kingsbury, adjacentTo, Neasden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Neasden
Context triple: [Kingsbury, adjacentTo, Neasden]
  • A. Neasden chosen
    Neasden is a suburban area in northwest London, England, known for its residential character and proximity to major roads and rail links.
  • B. Cheshunt
    Cheshunt is a town in Hertfordshire, England, situated just north of London and known as a commuter hub with rail links into the capital.
  • C. Hoddlesden
    Hoddlesden is a small village in Lancashire, England, situated in a rural valley setting and historically associated with textile manufacturing.
  • D. Bennetts End
    Bennetts End is a residential area and suburb located within the county of Hertfordshire in England.
  • E. Greenford
    Greenford is a suburban area in the London Borough of Ealing, known for its residential neighborhoods, parks, and transport links in West London.
  • 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_69d886cfc8e88190b05ba466edd35591 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3dc2683fc81908af2df9012addecb completed April 18, 2026, 7:31 p.m.
Created at: April 10, 2026, 5:35 a.m.