Triple
T10016180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A264 road |
E199500
|
entity |
| Predicate | passesThrough |
P225
|
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: [A264 road, passesThrough, Pembury]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pembury Context triple: [A264 road, passesThrough, Pembury]
-
A.
Pembury
chosen
Pembury is a village and civil parish in Kent, England, situated near the town of Royal Tunbridge Wells.
-
B.
Horbury
Horbury is a town in West Yorkshire, England, historically part of the Wakefield area and known for its industrial heritage and parish church.
-
C.
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.
-
D.
Norbury
Norbury is a suburban district in south London known for its residential character, diverse community, and good transport links into central London.
-
E.
Norbury
Norbury is a rural English village known for its scenic location along the Shropshire Union Canal and surrounding countryside.
- 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_69ca8315a1a08190ab310f25620f362b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd4ad3348190bae03cd37c787674 |
completed | April 2, 2026, 1:58 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2821b22488190913d743bc40a4c8e |
completed | April 5, 2026, 3:39 p.m. |
Created at: March 30, 2026, 8:52 p.m.