Triple
T18104859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rishworth branch line |
E433321
|
entity |
| Predicate | hasLocale |
P387
|
FINISHED |
| Object | Rishworth |
—
|
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: Rishworth | Statement: [Rishworth branch line, hasLocale, Rishworth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rishworth Context triple: [Rishworth branch line, hasLocale, Rishworth]
-
A.
Rishworth
chosen
Rishworth is a village in Calderdale, West Yorkshire, England, known historically for its former railway terminus on the Rishworth branch line.
-
B.
Blisworth
Blisworth is a village in Northamptonshire, England, known for its historic location on the Grand Union Canal near the Blisworth Tunnel.
-
C.
Rushworth
Rushworth is the middle name of Lord Jellicoe, a British naval officer and statesman who served as First Sea Lord during World War I.
-
D.
Rushworth
Rushworth is a small rural town in northern Victoria, Australia, known for its gold rush heritage and historic streetscape.
-
E.
Elsworth
Elsworth is a surname and given name of English origin, historically associated with various places and families in England.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddb9981c8190b33697fbcaa901b3 |
completed | April 19, 2026, 1:50 p.m. |
Created at: April 10, 2026, 10:28 a.m.