Triple
T20409266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington, County Durham, England |
E500546
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Usworth |
—
|
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: Usworth | Statement: [Washington, County Durham, England, hasPart, Usworth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Usworth Context triple: [Washington, County Durham, England, hasPart, Usworth]
-
A.
Usworth
chosen
Usworth is a residential locality within Washington in the metropolitan county of Tyne and Wear in North East England.
-
B.
Blisworth
Blisworth is a village in Northamptonshire, England, known for its historic location on the Grand Union Canal near the Blisworth Tunnel.
-
C.
Worsthorne
Worsthorne is a British surname most notably associated with journalist and commentator Peregrine Worsthorne.
-
D.
Cullingworth
Cullingworth is a village in West Yorkshire, England, situated near the town of Bingley and within commuting distance of Bradford.
-
E.
Mouldsworth
Mouldsworth is a village in Cheshire, England, served by a railway station on the Manchester–Chester line.
- 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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67a3e0c1c8190be39d7f09c839dfa |
completed | April 20, 2026, 7:10 p.m. |
Created at: April 16, 2026, 11:29 a.m.