Triple
T1279743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haslemere |
E27296
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | HASLEMERE |
E27296
|
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: HASLEMERE | Statement: [Haslemere, hasPostTown, HASLEMERE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HASLEMERE Context triple: [Haslemere, hasPostTown, HASLEMERE]
-
A.
Haslemere
chosen
Haslemere is a historic market town in the southwest of Surrey, England, near the borders with Hampshire and West Sussex.
-
B.
Harrold
Harrold is a given name and surname, used as a variant spelling of Harold.
-
C.
Hempton
Hempton is a small village in Norfolk, England, situated close to the market town of Fakenham.
-
D.
Hannington
Hannington is a small rural village in Wiltshire, England, known for its traditional English countryside setting and historic character.
-
E.
Godalming
Godalming is a historic market town in southeast England known for its picturesque streets, riverside setting, and role as a commuter hub for London.
- 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_69a496d3710c8190955dee8bc0dacb50 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c092eb688190bf42bbd59e4ff289 |
completed | March 1, 2026, 10:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69aca2f91b348190b2994af7edaf4f67 |
completed | March 7, 2026, 10:13 p.m. |
Created at: March 1, 2026, 7:50 p.m.