Triple
T11631658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milnsbridge |
E276411
|
entity |
| Predicate | hasNearbySettlement |
P4647
|
FINISHED |
| Object | Linthwaite |
E274874
|
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: Linthwaite | Statement: [Milnsbridge, hasNearbySettlement, Linthwaite]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Linthwaite Context triple: [Milnsbridge, hasNearbySettlement, Linthwaite]
-
A.
Linthwaite
chosen
Linthwaite is a village in West Yorkshire, England, situated in the Colne Valley to the southwest of Huddersfield.
-
B.
Horsforth
Horsforth is a suburban town in West Yorkshire, England, situated northwest of Leeds and known for its residential character and commuter links.
-
C.
Dewsbury
Dewsbury is a market town in West Yorkshire, England, situated between Leeds and Huddersfield on major rail and road routes.
-
D.
Saddleworth
Saddleworth is a civil parish and rural area in the Pennines of Greater Manchester, England, known for its moorland landscapes, historic villages, and traditional cultural events.
-
E.
Acomb
Acomb is a village in Northumberland, England, situated near Hexham and known for its rural character and historic surroundings.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25aa9188190ab13d79139f37e7e |
completed | April 10, 2026, 7:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ef135cde4881908d1cf9f752592d60 |
completed | April 27, 2026, 7:42 a.m. |
Created at: April 8, 2026, 9:39 p.m.