Triple
T22778032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterlooville |
E563756
|
entity |
| Predicate | hasNearbySettlement |
P4647
|
FINISHED |
| Object | Purbrook |
—
|
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: Purbrook | Statement: [Waterlooville, hasNearbySettlement, Purbrook]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Purbrook Context triple: [Waterlooville, hasNearbySettlement, Purbrook]
-
A.
Purbrook
chosen
Purbrook is a suburban village in Hampshire, England, situated near Portsmouth and forming part of the wider Havant area.
-
B.
Polebrook
Polebrook is a small rural village in Northamptonshire, England, known for its historic church and traditional English countryside setting.
-
C.
Bilbrook
Bilbrook is a village in Staffordshire, England, known as the place where geneticist Reginald Punnett died.
-
D.
Sutton Broad
Sutton Broad is a shallow freshwater lake in the Norfolk Broads of England, valued for its wildlife habitats and recreational boating.
-
E.
Giltbrook
Giltbrook is a village in Nottinghamshire, England, known for its retail park and proximity to the town of Kimberley.
- 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_69e24554497c819080b996e071de27c2 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17b631c6881908a6687920923dcf4 |
completed | April 29, 2026, 3:30 a.m. |
Created at: April 17, 2026, 3:28 p.m.