Triple
T6678208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A320 road |
E151908
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Chertsey |
E27353
|
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: Chertsey | Statement: [A320 road, connects, Chertsey]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chertsey Context triple: [A320 road, connects, Chertsey]
-
A.
Chertsey
chosen
Chertsey is a historic town in southeast England, known for its medieval abbey heritage and location on the River Thames.
-
B.
Isleworth
Isleworth is a suburban town in West London, England, known for hosting major media and broadcasting facilities.
-
C.
Esher
Esher is a suburban town in the borough of Elmbridge in Surrey, England, known for its affluent residential character and proximity to London.
-
D.
Teddington
Teddington is a suburban town in southwest London, England, known for its riverside location on the Thames and proximity to several royal parks.
-
E.
Sunbury-on-Thames
Sunbury-on-Thames is a suburban town on the River Thames in south-east England, historically part of Middlesex and now within the borough of Spelthorne.
- 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_69c687f830bc81909eb8b04dbb8450b1 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6b0f53af48190b0b25b61c3531158 |
completed | March 27, 2026, 4:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c9855a13d4819099ee6bf89566291f |
completed | March 29, 2026, 8:02 p.m. |
Created at: March 27, 2026, 2:03 p.m.