Triple

T6963975
Position Surface form Disambiguated ID Type / Status
Subject E1 E161440 entity
Predicate coversArea P175 FINISHED
Object Aldgate E303935 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: Aldgate | Statement: [E1, coversArea, Aldgate]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aldgate
Context triple: [E1, coversArea, Aldgate]
  • A. Aldgate chosen
    Aldgate is a central London Underground station in the City of London, serving as a key interchange and endpoint for multiple Tube lines.
  • B. Aldgate
    Aldgate is a small township in the Adelaide Hills region of South Australia, known for its leafy surroundings and village-style atmosphere.
  • C. Ludgate Hill
    Ludgate Hill is a historic street and one of the traditional high points in the City of London, forming part of the route between Fleet Street and St Paul's Cathedral.
  • D. Farringdon
    Farringdon is a small rural village in the East Hampshire district of Hampshire, England, known for its historic church and traditional countryside setting.
  • E. Farringdon
    Farringdon is a major central London railway and London Underground interchange station, serving as a key hub on routes including Thameslink and the Elizabeth line.
  • 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_69c68853cff881908439d488924a8283 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6daf2b7bc8190a3e73f3b24f0352b completed March 27, 2026, 7:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69c76a00ded081908db2a4d539e4e502 completed March 28, 2026, 5:41 a.m.
Created at: March 27, 2026, 2:30 p.m.