Triple
T21290761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A299 road |
E524781
|
entity |
| Predicate | serves |
P98
|
FINISHED |
| Object | Whitstable |
—
|
NE NERFINISHED |
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: Whitstable | Statement: [A299 road, serves, Whitstable]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Whitstable Context triple: [A299 road, serves, Whitstable]
-
A.
Whitstable
chosen
Whitstable is a coastal town on the north coast of Kent in southeast England, known for its historic oyster fishing industry and pebble beaches.
-
B.
Folkestone
Folkestone is a coastal town and port in Kent, England, known as a gateway to continental Europe via the Channel Tunnel and nearby ferry links.
-
C.
Brightlingsea
Brightlingsea is a coastal town in Essex, England, historically known for its maritime trade, shipbuilding, and association with the medieval Cinque Ports confederation.
-
D.
Hildenborough
Hildenborough is a village in Kent, England, situated near Tonbridge and known for its commuter links to London and surrounding towns.
-
E.
Richborough
Richborough is a historic site in Kent, England, known for its significant Roman remains and its role as a key gateway to Roman Britain.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b5171f6c8190a5d57201ede73811 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e736d9467881908ec5b1dec76e6f5d |
completed | April 21, 2026, 8:35 a.m. |
Created at: April 16, 2026, 4:04 p.m.