Triple
T8809382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brooklin |
E209617
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Pickering |
E99468
|
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: Pickering | Statement: [Brooklin, locatedNear, Pickering]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pickering Context triple: [Brooklin, locatedNear, Pickering]
-
A.
Pickering
chosen
Pickering is a suburban city in Southern Ontario, Canada, located just east of Toronto along Lake Ontario.
-
B.
Pickering
Pickering is a historic market town in North Yorkshire, England, known as a gateway to the North York Moors and for its heritage steam railway.
-
C.
Pickering
Pickering is an English-origin surname borne by numerous notable figures in science, politics, and the arts.
-
D.
Parkeston
Parkeston is a village and port area in Essex, England, situated near Harwich and known historically for its railway and maritime connections.
-
E.
Courtfield
Courtfield is a residential district within the Royal Borough of Kensington and Chelsea in west London, known for its affluent character and proximity to central London amenities.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fd69df4819091e9a7dad87265a4 |
completed | March 31, 2026, 11:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf6faa5dbc819083ecfbbb261cbc44 |
completed | April 3, 2026, 7:43 a.m. |
Created at: March 30, 2026, 6:45 p.m.