Triple
T11635948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackwater, Hampshire |
E276518
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Sandhurst |
E249229
|
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: Sandhurst | Statement: [Blackwater, Hampshire, adjacentTo, Sandhurst]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sandhurst Context triple: [Blackwater, Hampshire, adjacentTo, Sandhurst]
-
A.
Sandhurst
Sandhurst is a village in Kent, England, known for its rural character and traditional English countryside setting.
-
B.
Sandhurst
chosen
Sandhurst is a town in Berkshire, England, best known as the home of the Royal Military Academy Sandhurst, the British Army’s premier officer training centre.
-
C.
Sandhurst
Sandhurst was the former name of the Australian city now known as Bendigo, a major gold rush settlement in Victoria.
-
D.
Sandhurst
Sandhurst is an affluent, predominantly residential suburb in Sandton, Johannesburg, known for its large estates and high-end real estate.
-
E.
Aldershot
Aldershot is a town in Hampshire, England, historically known as a major British Army garrison and military center.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25d80208190b33e95db2e7cc276 |
completed | April 10, 2026, 7:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ee87c0fe4881908dda9c493d958500 |
completed | April 26, 2026, 9:46 p.m. |
Created at: April 8, 2026, 9:39 p.m.