Triple
T8465898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Township of King |
E200159
|
entity |
| Predicate | hasCommunity |
P2605
|
FINISHED |
| Object | Kettleby |
E436686
|
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: Kettleby | Statement: [Township of King, hasCommunity, Kettleby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kettleby Context triple: [Township of King, hasCommunity, Kettleby]
-
A.
Kettleby
chosen
Kettleby is a small rural community in King Township, Ontario, known for its historic character and scenic countryside.
-
B.
Kettletoft
Kettletoft is the main village and administrative hub on the Orkney island of Sanday in Scotland.
-
C.
Horbury
Horbury is a town in West Yorkshire, England, historically part of the Wakefield area and known for its industrial heritage and parish church.
-
D.
Cronkhill
Cronkhill is a notable early 19th-century Italianate-style country villa in Shropshire, England, recognized as one of the first examples of this architectural style in the country.
-
E.
Ketteringham
Ketteringham is a small village and civil parish in Norfolk, England, known for its rural character and historic parish church.
- 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.