Triple
T7162761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Attleborough railway station |
E166985
|
entity |
| Predicate | serves |
P98
|
FINISHED |
| Object | Attleborough |
E166985
|
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: Attleborough | Statement: [Attleborough railway station, serves, Attleborough]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Attleborough Context triple: [Attleborough railway station, serves, Attleborough]
-
A.
Attleborough
chosen
Attleborough is a market town and civil parish in the English county of Norfolk.
-
B.
Downham
Downham is a picturesque rural village in Lancashire, England, known for its unspoiled traditional character and scenic setting near Pendle Hill.
-
C.
Downham
Downham is a residential district in southeast London known for its interwar housing estates and suburban character within the London Borough of Lewisham.
-
D.
Harleston
Harleston is a village and civil parish located in the county of Suffolk in eastern England.
-
E.
Bridport
Bridport is a historic market town in southwest England known for its rope-making heritage and proximity to the Jurassic Coast.
- 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_69c68888c10c819095e0383020225758 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e82feee481908fa180ea8c9924fa |
completed | March 27, 2026, 8:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7adc4b7648190969fab0351f9fd22 |
completed | March 28, 2026, 10:30 a.m. |
Created at: March 27, 2026, 2:47 p.m.