Triple
T15511624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Botley |
E368722
|
entity |
| Predicate | isLocatedNear |
P350
|
FINISHED |
| Object | Bursledon |
E375477
|
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: Bursledon | Statement: [Botley, isLocatedNear, Bursledon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bursledon Context triple: [Botley, isLocatedNear, Bursledon]
-
A.
Bursledon
chosen
Bursledon is a village in Hampshire, England, known for its maritime heritage on the River Hamble and its historic shipbuilding and yachting connections.
-
B.
Basildon
Basildon is a large town in Essex, England, known as a post-war new town and a major commercial and residential centre within the East of England.
-
C.
Wivenhoe
Wivenhoe is a suburb within the coastal city of Burnie in north-west Tasmania, Australia.
-
D.
Wivenhoe
Wivenhoe is a riverside town in Essex, England, known for its historic maritime character, artistic community, and proximity to the University of Essex.
-
E.
Wivenhoe
Wivenhoe is a locality in Queensland, Australia, situated near the Wivenhoe Dam and associated with the broader Sunshine Coast region.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e04030c0208190a1931ea130075603 |
completed | April 16, 2026, 1:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff4c3618dc8190aab243bb61d198ce |
completed | May 9, 2026, 3:01 p.m. |
Created at: April 10, 2026, 3:56 a.m.