Triple
T4740476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A2 road |
E105226
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Sittingbourne |
E48172
|
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: Sittingbourne | Statement: [A2 road, passesThrough, Sittingbourne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sittingbourne Context triple: [A2 road, passesThrough, Sittingbourne]
-
A.
Sittingbourne
chosen
Sittingbourne is an industrial and commuter town in southeast England, located in the county of Kent.
-
B.
Sittingbourne and Sheppey
Sittingbourne and Sheppey is a UK parliamentary constituency in Kent that covers the town of Sittingbourne and the Isle of Sheppey.
-
C.
Uckfield
Uckfield is a small market town in East Sussex, England, known for its historic high street and role as a local commercial and commuter hub.
-
D.
Henham
Henham is a small rural village located in the English county of Suffolk.
-
E.
Burnham-on-Crouch
Burnham-on-Crouch is a riverside town in Essex, England, known for its sailing heritage and annual regattas on the River Crouch.
- 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64a5f3548190a6acf1dcfd64d11d |
completed | March 20, 2026, 3:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be3a211d2c8190a87ad81ef90dcf3b |
completed | March 21, 2026, 6:26 a.m. |
Created at: March 20, 2026, 1:19 p.m.