Triple
T23280864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sutton Common railway station |
E588857
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Sutton |
—
|
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: Sutton | Statement: [Sutton Common railway station, locatedIn, Sutton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sutton Context triple: [Sutton Common railway station, locatedIn, Sutton]
-
A.
Sutton
chosen
Sutton is a large suburban town in South London, England, known as the principal settlement of the London Borough of Sutton.
-
B.
Sutton
Sutton is a village and civil parish located in the county of Suffolk in eastern England.
-
C.
Sutton
Sutton is a small rural village in New South Wales, Australia, located near Canberra and known for its quiet countryside setting.
-
D.
Sutton
Sutton is a small unincorporated community in Alaska known for its scenic Matanuska River valley setting and historic coal-mining roots.
-
E.
Sutton
Sutton is a district within the Metropolitan Borough of St Helens in Merseyside, England, known historically for its coal mining and industrial heritage.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19642b46481909fd455acd2155792 |
completed | April 29, 2026, 5:25 a.m. |
Created at: April 17, 2026, 4:56 p.m.