Triple
T20175174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tupton |
E492070
|
entity |
| Predicate | hasNearbySettlement |
P4647
|
FINISHED |
| Object | Wingerworth |
—
|
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: Wingerworth | Statement: [Tupton, hasNearbySettlement, Wingerworth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wingerworth Context triple: [Tupton, hasNearbySettlement, Wingerworth]
-
A.
Wingerworth
chosen
Wingerworth is a large suburban village in Derbyshire, England, situated just south of Chesterfield and known for its residential character and local amenities.
-
B.
Willingdon
Willingdon is a village in East Sussex, England, situated near the town of Hailsham.
-
C.
Highworth
Highworth is a historic market town in Wiltshire, England, known for its elevated position and traditional architecture.
-
D.
Watlington
Watlington is a residential suburb located within the city of Timaru in the Canterbury region of New Zealand.
-
E.
Watlington
Watlington is a small historic market town in Oxfordshire, England, known for its traditional high street and location near the Chiltern Hills.
- 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.