Triple
T6172164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hampton (London Borough of Richmond upon Thames) |
E137727
|
entity |
| Predicate | hasNeighbour |
P5707
|
FINISHED |
| Object | Hampton Wick |
E238277
|
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: Hampton Wick | Statement: [Hampton (London Borough of Richmond upon Thames), hasNeighbour, Hampton Wick]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hampton Wick Context triple: [Hampton (London Borough of Richmond upon Thames), hasNeighbour, Hampton Wick]
-
A.
Hampton Wick
chosen
Hampton Wick is a suburban riverside area in southwest London, situated on the north bank of the River Thames opposite Kingston upon Thames.
-
B.
Henham
Henham is a small rural village located in the English county of Suffolk.
-
C.
Brockham
Brockham is a picturesque village in Surrey, England, known for its traditional village green and historic rural character.
-
D.
Hanham
Hanham is a suburban village and residential area on the eastern edge of Bristol in South West England.
-
E.
Chobham
Chobham is a village and civil parish in Surrey, England, known for its rural character, common land, and historic buildings.
- 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d9319548190980c99f692bd4115 |
completed | March 22, 2026, 9:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c141ad559881909076b6ab34b14f2b |
completed | March 23, 2026, 1:35 p.m. |
Created at: March 22, 2026, 4:18 p.m.