Triple
T15305987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haslemere |
E365898
|
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.
Hackham
Hackham is a southern suburb of Adelaide in South Australia, situated within the local government area of the City of Onkaparinga.
-
C.
Hazlemere
Hazlemere is a suburban village and civil parish in Buckinghamshire, England, situated near High Wycombe.
-
D.
Laleham
Laleham is a riverside village in Surrey, England, situated on the River Thames and known for its historic church, green spaces, and residential character.
-
E.
Bookham
Bookham is a village in Surrey, England, known for its residential character and proximity to the North Downs countryside.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03ccef14c819099c5ebe962e7f867 |
completed | April 16, 2026, 1:35 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fef89d961481909be8dcc2864982c9 |
completed | May 9, 2026, 9:04 a.m. |
Created at: April 10, 2026, 3:16 a.m.