Triple
T21539843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langwith |
E531451
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Langwith Junction |
—
|
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: Langwith Junction | Statement: [Langwith, locatedNear, Langwith Junction]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Langwith Junction Context triple: [Langwith, locatedNear, Langwith Junction]
-
A.
Langwith Junction
chosen
Langwith Junction is a residential area forming part of the former mining community around Shirebrook in Derbyshire, England.
-
B.
Evercreech Junction
Evercreech Junction was a former railway station and key junction on the Somerset and Dorset Joint Railway in Somerset, England.
-
C.
Coppermill Junction
Coppermill Junction is a key railway junction in northeast London where multiple routes on the Lea Valley lines converge and diverge.
-
D.
Halwill Junction
Halwill Junction is a small rural village in West Devon, England, historically known for its former railway junction on the North Cornwall and Okehampton lines.
-
E.
Horbury Junction
Horbury Junction is a residential suburb of Horbury in West Yorkshire, England, known for its proximity to major road and rail links.
- 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_69e0c45f17148190949c330ab9c27706 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee9d119e0c8190a207c0e8ae328a95 |
completed | April 26, 2026, 11:17 p.m. |
Created at: April 16, 2026, 6:28 p.m.