Triple
T6354236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clay Cross |
E142950
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Alfreton |
E118920
|
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: Alfreton | Statement: [Clay Cross, near, Alfreton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alfreton Context triple: [Clay Cross, near, Alfreton]
-
A.
Alfreton
chosen
Alfreton is a town in the Amber Valley district of Derbyshire, England, with historical roots in coal mining and industry.
-
B.
Hednesford
Hednesford is a small town in Staffordshire, England, situated near Cannock Chase and known historically for its coal mining heritage.
-
C.
Retford
Retford is a historic market town in the English county of Nottinghamshire, known for its traditional town center and transport links.
-
D.
Rugeley
Rugeley is a market town in Staffordshire, England, historically known for its coal mining industry and location on the River Trent.
-
E.
Wrottesley
Wrottesley is an English surname historically associated with a prominent aristocratic family and the title Baron Wrottesley.
- 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_69c008d6dcbc8190aa1c2f1fd8916b42 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067e0cf1081908ee7e83b9dcf740e |
completed | March 22, 2026, 10:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c60459a7c081909b551dcf1735bf75 |
completed | March 27, 2026, 4:15 a.m. |
Created at: March 22, 2026, 4:31 p.m.