Triple
T20175173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tupton |
E492070
|
entity |
| Predicate | hasNearbySettlement |
P4647
|
FINISHED |
| Object | Clay Cross |
—
|
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: Clay Cross | Statement: [Tupton, hasNearbySettlement, Clay Cross]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Clay Cross Context triple: [Tupton, hasNearbySettlement, Clay Cross]
-
A.
Clay Cross
chosen
Clay Cross is a former coal mining and industrial town in North East Derbyshire, England.
-
B.
Bolsover
Bolsover is a historic market town in England best known for its hilltop Bolsover Castle and its location within the county of Derbyshire.
-
C.
Keyworth
Keyworth is a large village in Nottinghamshire, England, functioning as a commuter settlement near Nottingham with local amenities and community facilities.
-
D.
Rothwell
Rothwell is a town in Northamptonshire, England, situated near Kettering and known for its historic market heritage.
-
E.
Rothwell
Rothwell is a town in West Yorkshire, England, situated near Leeds and historically known for its coal mining and market traditions.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e668eaa3b88190bef4f2db0125fdfc |
completed | April 20, 2026, 5:56 p.m. |
Created at: April 11, 2026, 11:36 p.m.