Triple
T18111305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brighton to Portsmouth line |
E433480
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Barnham |
—
|
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: Barnham | Statement: [Brighton to Portsmouth line, passesThrough, Barnham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Barnham Context triple: [Brighton to Portsmouth line, passesThrough, Barnham]
-
A.
Barnham
chosen
Barnham is a village and civil parish in West Sussex, England, known for its railway junction and rural surroundings.
-
B.
Henham
Henham is a small rural village located in the English county of Suffolk.
-
C.
Brockham
Brockham is a picturesque village in Surrey, England, known for its traditional village green and historic rural character.
-
D.
Bedhampton
Bedhampton is a suburban area and former village in Hampshire, England, situated near Havant on the south coast.
-
E.
Hildenborough
Hildenborough is a village in Kent, England, situated near Tonbridge and known for its commuter links to London and surrounding towns.
- 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_69e4ddd2038081909515fb6d17495cbf |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 10:28 a.m.