Triple

T2964881
Position Surface form Disambiguated ID Type / Status
Subject Ealing, London E80137 entity
Predicate hasPart P35 FINISHED
Object Ealing Broadway E286903 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: Ealing Broadway | Statement: [Ealing, London, hasPart, Ealing Broadway]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ealing Broadway
Context triple: [Ealing, London, hasPart, Ealing Broadway]
  • A. Ealing Broadway chosen
    Ealing Broadway is a major transport hub and commercial center in west London, served by both London Underground and National Rail services.
  • B. Ladbroke Grove
    Ladbroke Grove is a vibrant area in West London known for its multicultural community, street markets, and proximity to the Notting Hill Carnival.
  • C. Earl's Court
    Earl's Court is a London Underground station in West London that functions as a major interchange on the District and Piccadilly lines.
  • D. Holborn
    Holborn is a historic district in central London known for its legal institutions, commercial streets, and proximity to the City and West End.
  • E. Leicester Square
    Leicester Square is a famous pedestrianized square in London’s West End, known for its cinemas, theatres, and entertainment venues.
  • 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_69ad8b1341848190bd19dbf46892887d completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad9958b1e48190a77f37bf63333c5b completed March 8, 2026, 3:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69b108e14e288190bcca59b2d8132996 completed March 11, 2026, 6:17 a.m.
Created at: March 8, 2026, 2:58 p.m.