Triple

T14414772
Position Surface form Disambiguated ID Type / Status
Subject Leytonstone E357420 entity
Predicate near P350 FINISHED
Object Forest Gate E413138 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: Forest Gate | Statement: [Leytonstone, near, Forest Gate]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Forest Gate
Context triple: [Leytonstone, near, Forest Gate]
  • A. Forest Gate chosen
    Forest Gate is a residential district in the London Borough of Newham, known for its diverse community and proximity to Stratford and the Queen Elizabeth Olympic Park.
  • B. Stone Gate
    Stone Gate is a historic medieval city gate in Zagreb’s Upper Town, renowned as a religious shrine and one of the city’s most iconic landmarks.
  • C. Valley Gates
    Valley Gates is a notable entrance area within Franklin Park in Boston, serving as one of the park’s key access points and landscape features.
  • D. Starr Gate
    Starr Gate is the southern coastal terminus of Blackpool’s tram network, serving as a key gateway for visitors arriving at the resort town.
  • E. Foog’s Gate
    Foog’s Gate is a historic entrance within Edinburgh Castle, serving as one of the main access points to the fortress complex.
  • 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_69d82793421c8190861eb0e673b085de completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de90cc99208190a2313b1acfb5d802 completed April 14, 2026, 7:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd552a75ec8190b966d509d315ca60 completed May 8, 2026, 3:14 a.m.
Created at: April 10, 2026, 1:17 a.m.