Triple
T8459463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Pickering |
E200004
|
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: [City of Pickering, hasNeighbourhood, Amberlea]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amberlea Context triple: [City of 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.
Amberley
Amberley is a picturesque village in West Sussex, England, known for its historic cottages, castle, and scenic setting in the South Downs near the River Arun.
-
C.
Brockham
Brockham is a picturesque village in Surrey, England, known for its traditional village green and historic rural character.
-
D.
Buckhaven
Buckhaven is a coastal town in eastern Scotland, situated on the Firth of Forth in the historic county of Fife.
-
E.
Sunningdale
Sunningdale is an affluent village in Berkshire, England, known for its prestigious golf courses and leafy residential character.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe49e036c8190abb50ca272266ca6 |
completed | March 31, 2026, 3:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce1df214ac8190b59daa88e3a930bc |
completed | April 2, 2026, 7:42 a.m. |
Created at: March 30, 2026, 6:10 p.m.