Triple

T4395163
Position Surface form Disambiguated ID Type / Status
Subject Pickering E99468 entity
Predicate hasNeighbourhood P4813 FINISHED
Object Amberlea E222083 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: Amberlea | Statement: [Pickering, hasNeighbourhood, Amberlea]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Amberlea
Context triple: [Pickering, hasNeighbourhood, Amberlea]
  • A. Amberlea chosen
    Amberlea is a residential neighbourhood located in the city of Pickering in the Greater Toronto Area of Ontario, Canada.
  • B. Brockham
    Brockham is a picturesque village in Surrey, England, known for its traditional village green and historic rural character.
  • C. Buckhaven
    Buckhaven is a coastal town in eastern Scotland, situated on the Firth of Forth in the historic county of Fife.
  • D. Sunningdale
    Sunningdale is an affluent village in Berkshire, England, known for its prestigious golf courses and leafy residential character.
  • E. Edgemead
    Edgemead is a planned residential suburb in the northern part of Cape Town, South Africa, known for its garden-city layout and family-oriented community.
  • 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_69b345506b408190b0e3dee616738a7d completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b352ab928c81909f4406d5df3e081b completed March 12, 2026, 11:56 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5e536e1848190a2517ab351adfe48 completed March 14, 2026, 10:46 p.m.
Created at: March 12, 2026, 11:20 p.m.