Triple
T22736583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Havant Park |
E562286
|
entity |
| Predicate | category |
P87
|
FINISHED |
| Object | Havant |
—
|
NE NERFINISHED |
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 Park, category, Havant]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Havant Context triple: [Havant Park, category, 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.
Fordingbridge
Fordingbridge is a small historic town on the River Avon in Hampshire, England, known for its medieval stone bridge and proximity to the New Forest.
-
D.
Basingstoke
Basingstoke is a large town in Hampshire, England, known as a major commercial and retail centre with significant modern development and transport links.
-
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 (2 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_69e24550859c81908727d91efc3a81b4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1796fc2a88190a4d86b421345b088 |
completed | April 29, 2026, 3:22 a.m. |
Created at: April 17, 2026, 3:22 p.m.