Triple
T7036185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Borough of Sutton |
E163390
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Sutton |
E141441
|
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: Sutton | Statement: [London Borough of Sutton, contains, Sutton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sutton Context triple: [London Borough of Sutton, contains, Sutton]
-
A.
Sutton
Sutton is a civil parish in Cheshire, England, forming part of the rural area around the town of Macclesfield.
-
B.
Sutton
Sutton is a small rural village located within the district of West Oxfordshire in England.
-
C.
Sutton
Sutton is a common English surname borne by numerous notable individuals across various fields.
-
D.
Sutton
chosen
Sutton is a large suburban town in South London, England, known as the principal settlement of the London Borough of Sutton.
-
E.
Sutton
Sutton is a small community within the town of Georgina in Ontario, Canada, known for its proximity to Lake Simcoe and its role as a local service and recreational hub.
- 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_69c6885e7c1c8190be32a8f79ab4e0cf |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e220508c8190b8950cf38280b8c2 |
completed | March 27, 2026, 8:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c78863c2fc8190b9b54613968742e1 |
completed | March 28, 2026, 7:50 a.m. |
Created at: March 27, 2026, 2:36 p.m.