Triple
T2986367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A21 road |
E80634
|
entity |
| Predicate | passesNear |
P416
|
FINISHED |
| Object | Pembury |
E126967
|
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: Pembury | Statement: [A21 road, passesNear, Pembury]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pembury Context triple: [A21 road, passesNear, Pembury]
-
A.
Pembury
chosen
Pembury is a village and civil parish in Kent, England, situated near the town of Royal Tunbridge Wells.
-
B.
Pulborough
Pulborough is a large rural village and civil parish in the Arun district of West Sussex, England, known for its position on the River Arun and proximity to the South Downs.
-
C.
Pangbourne
Pangbourne is a picturesque village on the River Thames in Berkshire, England, known for its literary associations and scenic rural charm.
-
D.
Haslemere
Haslemere is a historic market town in the southwest of Surrey, England, near the borders with Hampshire and West Sussex.
-
E.
Wraysbury
Wraysbury is a village and civil parish in Berkshire, England, situated near the River Thames and known for its historic sites and proximity to Windsor.
- 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_69ad8b16c3488190b47b6aa7a59a335b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99c76dfc8190b08bd6110ffabf25 |
completed | March 8, 2026, 3:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b108fb46b08190bcbd00e69cf06047 |
completed | March 11, 2026, 6:17 a.m. |
Created at: March 8, 2026, 2:59 p.m.