Triple
T11212833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS postcode area |
E265350
|
entity |
| Predicate | covers |
P1393
|
FINISHED |
| Object | Thundersley |
E658548
|
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: Thundersley | Statement: [SS postcode area, covers, Thundersley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Thundersley Context triple: [SS postcode area, covers, Thundersley]
-
A.
Thundersley
chosen
Thundersley is a suburban area and former village in Essex, England, now largely residential and integrated into the Southend-on-Sea commuter belt.
-
B.
Teversham
Teversham is a small village and civil parish located near Cambridge in the South Cambridgeshire district of England.
-
C.
Thelnetham
Thelnetham is a small rural village and civil parish in the English county of Suffolk, known for its traditional countryside character and historic buildings.
-
D.
Wrottesley
Wrottesley is an English surname historically associated with a prominent aristocratic family and the title Baron Wrottesley.
-
E.
Helsby
Helsby is a village and civil parish in Cheshire, England, known for its railway station on the Manchester–Chester line and its prominent sandstone hill, Helsby Hill.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d7f47c8190b78c640ff1a01943 |
completed | April 9, 2026, 5:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e497569efc8190b8e9cb6b1db3f94d |
completed | April 19, 2026, 8:50 a.m. |
Created at: April 8, 2026, 9:30 p.m.