Triple
T20085319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horbury |
E500110
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Ossett |
—
|
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: Ossett | Statement: [Horbury, locatedNear, Ossett]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ossett Context triple: [Horbury, locatedNear, Ossett]
-
A.
Ossett
chosen
Ossett is a market town in northern England that forms part of the City of Wakefield metropolitan borough in West Yorkshire.
-
B.
Hartshill
Hartshill is a residential suburb and ward of Stoke-on-Trent in Staffordshire, England, known for its Victorian architecture and proximity to the city centre.
-
C.
Rushton
Rushton is a small rural village and civil parish in Cheshire, England, known for its countryside setting and historic character.
-
D.
Glossop
Glossop is a market town in Derbyshire, England, situated on the edge of the Peak District and historically associated with the textile industry.
-
E.
Helsby
Helsby is a village and civil parish in Cheshire, England, known for its railway station on the Manchester–Chester line and its prominent sandstone hill, Helsby Hill.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6655ae9ec8190bde2f17452639de8 |
completed | April 20, 2026, 5:41 p.m. |
Created at: April 11, 2026, 3:41 p.m.