Triple
T10016173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A264 road |
E199500
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Felbridge |
E337353
|
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: Felbridge | Statement: [A264 road, passesThrough, Felbridge]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Felbridge Context triple: [A264 road, passesThrough, Felbridge]
-
A.
Felbridge
chosen
Felbridge is a village and civil parish in Surrey, England, situated near East Grinstead and known for its rural character and local historic buildings.
-
B.
Gadebridge
Gadebridge is a residential area and suburb of Hemel Hempstead in Hertfordshire, England.
-
C.
Gairneybridge
Gairneybridge is a small settlement in the historic county of Kinross-shire in central Scotland.
-
D.
Gorebridge
Gorebridge is a former mining village in Midlothian, Scotland, known for its historic railway connections and proximity to Edinburgh.
-
E.
Sleights Bridge
Sleights Bridge is a historic road bridge in the village of Sleights, North Yorkshire, England, carrying traffic across the River Esk.
- 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_69d26a99971081908397f06c0ce913d0 |
completed | April 5, 2026, 1:58 p.m. |
Created at: March 30, 2026, 8:52 p.m.