Triple
T22264274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rochester and Strood |
E550307
|
entity |
| Predicate | hasMajorSettlement |
P316
|
FINISHED |
| Object | Cuxton |
—
|
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: Cuxton | Statement: [Rochester and Strood, hasMajorSettlement, Cuxton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cuxton Context triple: [Rochester and Strood, hasMajorSettlement, Cuxton]
-
A.
Cuxton
chosen
Cuxton is a village and civil parish in the Medway unitary authority of Kent, England, situated on the River Medway.
-
B.
Buxworth
Buxworth is a small village in the High Peak district of Derbyshire, England, known historically for its canal basin and industrial heritage.
-
C.
Hauxton
Hauxton is a small village in South Cambridgeshire, England, situated just southwest of Cambridge and known for its rural character and proximity to major transport routes.
-
D.
Coryton
Coryton is a suburban area and railway terminus in Cardiff, Wales, served by local commuter trains.
-
E.
Cassington
Cassington is a small rural village in Oxfordshire, England, known for its historic church and traditional English countryside setting.
- 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_69e11e42adb8819087714772ea606709 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f141ba5c9481909e24067133918ae2 |
completed | April 28, 2026, 11:24 p.m. |
Created at: April 16, 2026, 8:39 p.m.