Triple
T22451224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoresy |
E554993
|
entity |
| Predicate | filmingLocation |
P40
|
FINISHED |
| Object | Sudbury, Ontario |
—
|
NE NERFINISHED |
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: Sudbury, Ontario | Statement: [Shoresy, filmingLocation, Sudbury, Ontario]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sudbury, Ontario Context triple: [Shoresy, filmingLocation, Sudbury, Ontario]
-
A.
Sudbury
Sudbury is a suburban area in northwest London, England, known for its residential character and proximity to Wembley.
-
B.
Sudbury
Sudbury is a small rural town in Rutland County, Vermont, known for its scenic landscapes and quiet, agricultural character.
-
C.
Sudbury
Sudbury is a historic market town in Suffolk, England, known for its medieval architecture and association with painter Thomas Gainsborough.
-
D.
Sudbury
chosen
Sudbury is a major city in northern Ontario, Canada, known for its mining industry and numerous surrounding lakes.
-
E.
East Sudbury
East Sudbury was the former name of the Massachusetts town now known as Wayland, a historic community in Middlesex County.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b4ba6a88190a0a79e2c20fa8c08 |
completed | April 29, 2026, 1:13 a.m. |
Created at: April 16, 2026, 8:48 p.m.