Triple
T5991552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Havant |
E133361
|
entity |
| Predicate | postTown |
P2711
|
FINISHED |
| Object | HAVANT |
E133361
|
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: HAVANT | Statement: [Havant, postTown, HAVANT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HAVANT Context triple: [Havant, postTown, HAVANT]
-
A.
Havant
chosen
Havant is a market town and borough in south-east England, situated between Portsmouth and Chichester near the south coast.
-
B.
Fareham
Fareham is a market town in southern England situated between the cities of Southampton and Portsmouth.
-
C.
Hove
Hove is a coastal town in East Sussex, England, forming part of the city of Brighton and Hove on the south coast.
-
D.
Havant Deanery
Havant Deanery is an administrative division of the Church of England within the Diocese of Portsmouth, grouping together local parishes in and around the Havant area.
-
E.
Basingstoke
Basingstoke is a large town in Hampshire, England, known as a major commercial and retail centre with significant modern development and transport links.
- 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_69c0087010d081908bb8142342d63330 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04e8fd030819095a4f3b3d425ec21 |
completed | March 22, 2026, 8:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c10861c0bc8190b6290d7363f4264a |
completed | March 23, 2026, 9:31 a.m. |
Created at: March 22, 2026, 4:05 p.m.