Triple

T13847998
Position Surface form Disambiguated ID Type / Status
Subject Neston E332858 entity
Predicate hasSuburb P747 FINISHED
Object Parkgate E953052 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: Parkgate | Statement: [Neston, hasSuburb, Parkgate]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Parkgate
Context triple: [Neston, hasSuburb, Parkgate]
  • A. Parkgate chosen
    Parkgate is a coastal village on the Wirral Peninsula in Cheshire, England, known for its saltmarsh views over the Dee Estuary and its history as a former port.
  • B. Churchgate
    Churchgate is a prominent railway terminus and commercial locality in South Mumbai, serving as a key hub for the city's suburban rail network.
  • C. Northgate
    Northgate is a residential suburb in the inner north-eastern area of Adelaide, South Australia.
  • D. Northgate
    Northgate is a neighborhood in north Seattle, Washington, known as a major commercial and transit hub that includes one of the city’s first shopping malls and a key light rail terminus.
  • E. Northgate
    Northgate is a residential neighbourhood and local community area within the town of Crawley in West Sussex, England.
  • 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_69d81c5ba13c8190839315f54768acfd completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de02b2a9788190b164760adec64ef6 completed April 14, 2026, 9:02 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7c0f189008190bb9afeef42564a33 completed May 3, 2026, 9:41 p.m.
Created at: April 9, 2026, 10:14 p.m.