Triple
T8465894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Township of King |
E200159
|
entity |
| Predicate | hasCommunity |
P2605
|
FINISHED |
| Object | Nobleton |
E439483
|
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: Nobleton | Statement: [Township of King, hasCommunity, Nobleton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nobleton Context triple: [Township of King, hasCommunity, 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 residential suburb within the city of Newcastle in New South Wales, Australia, known for its local parks, schools, and community facilities.
-
C.
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.
-
D.
Bowmanville
Bowmanville is a community in Ontario, Canada, serving as the main urban and administrative centre of the municipality of Clarington in the Durham Region.
-
E.
Clarington
Clarington is a largely suburban and rural municipality in Ontario, Canada, located at the eastern edge of the Greater Toronto Area.
- 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_69cbe4d17ec8819093becdaec750aff5 |
completed | March 31, 2026, 3:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce39e0d7788190add03271c940e1ff |
completed | April 2, 2026, 9:41 a.m. |
Created at: March 30, 2026, 6:11 p.m.