Triple
T11479302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hove |
E272100
|
entity |
| Predicate | postTown |
P2711
|
FINISHED |
| Object | HOVE |
E272100
|
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: HOVE | Statement: [Hove, postTown, HOVE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HOVE Context triple: [Hove, postTown, HOVE]
-
A.
Hove
chosen
Hove is a coastal town in East Sussex, England, forming part of the city of Brighton and Hove on the south coast.
-
B.
Hove
Hove is a small, affluent municipality in the Belgian province of Antwerp, known for its residential character and green surroundings.
-
C.
Havant
Havant is a market town and borough in south-east England, situated between Portsmouth and Chichester near the south coast.
-
D.
Hassocks
Hassocks is a large village and civil parish in the Mid Sussex district of West Sussex, England, situated just north of the South Downs and known for its commuter links to Brighton and London.
-
E.
Waterlooville
Waterlooville is a town in Hampshire, England, situated north of Portsmouth and known primarily as a residential and commuter area.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8294f0e948190b2e106beb86e4b2c |
completed | April 9, 2026, 10:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5e970743c8190a5be4d59d1b941d6 |
completed | April 20, 2026, 8:53 a.m. |
Created at: April 8, 2026, 9:36 p.m.