Triple
T18264605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pottageville |
E437450
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Nobleton |
—
|
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: Nobleton | Statement: [Pottageville, near, Nobleton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nobleton Context triple: [Pottageville, near, Nobleton]
-
A.
Nobleton
chosen
Nobleton is a small community that serves as one of the local settlements within the jurisdiction of King, Ontario, Canada.
-
B.
Lambton
Lambton is a central district of Wellington, New Zealand, known for its commercial hub Lambton Quay and proximity to the city's waterfront and government precinct.
-
C.
Lambton
Lambton is a residential suburb within the city of Newcastle in New South Wales, Australia, known for its local parks, schools, and community facilities.
-
D.
Lambton
Lambton is a residential neighbourhood in Toronto, Ontario, known for its proximity to the Humber River and its mix of historic and suburban housing.
-
E.
Lambton
Lambton is a residential area within Washington in the metropolitan county of Tyne and Wear, England.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ff78b188819081da8e1d389c6c79 |
completed | April 19, 2026, 4:14 p.m. |
Created at: April 10, 2026, 10:34 a.m.