Triple
T13043713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dover–Ramsgate line |
E327262
|
entity |
| Predicate | serves |
P98
|
FINISHED |
| Object | Kearsney |
E676565
|
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: Kearsney | Statement: [Dover–Ramsgate line, serves, Kearsney]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kearsney Context triple: [Dover–Ramsgate line, serves, Kearsney]
-
A.
Kearsney
chosen
Kearsney is a small village in Kent, England, situated near Dover and known for its proximity to Kearsney Abbey and the River Dour.
-
B.
Kearsley
Kearsley is a town in Greater Manchester, England, historically part of Lancashire and known for its industrial heritage.
-
C.
Kingswood
Kingswood is a suburban town in South Gloucestershire, England, forming part of the greater Bristol urban area.
-
D.
Kingswood
Kingswood is a suburban area in southwest Dublin, Ireland, served by the Luas light rail system.
-
E.
Kingswood
Kingswood is a suburban residential area in the borough of Reigate and Banstead in Surrey, England, known for its leafy streets and affluent character.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98050157c8190bb8c640b759ac2b7 |
completed | April 10, 2026, 10:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6cbd720248190a23a07dadc7e1348 |
completed | May 3, 2026, 4:15 a.m. |
Created at: April 9, 2026, 8:56 p.m.