Triple
T15361947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brockenhurst |
E367308
|
entity |
| Predicate | postTown |
P2711
|
FINISHED |
| Object | BROCKENHURST |
E367308
|
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: BROCKENHURST | Statement: [Brockenhurst, postTown, BROCKENHURST]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BROCKENHURST Context triple: [Brockenhurst, postTown, BROCKENHURST]
-
A.
Brockenhurst
chosen
Brockenhurst is a village in Hampshire, England, situated in the New Forest and served by a major railway station on the South West Main Line.
-
B.
Brookhouse
Brookhouse is a small rural village in Lancashire, England, situated within the civil parish of Caton-with-Littledale near the River Lune.
-
C.
Brockham
Brockham is a picturesque village in Surrey, England, known for its traditional village green and historic rural character.
-
D.
Crowhurst
Crowhurst is a small rural village and civil parish in Surrey, England, known for its historic church and countryside setting.
-
E.
Brantham
Brantham is a village and civil parish in Suffolk, England, situated near the River Stour close to the Essex border.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e479f188190bbbc3dcd73853e02 |
completed | April 16, 2026, 1:41 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff0b4a181c8190bffc1ac1a86e215d |
completed | May 9, 2026, 10:24 a.m. |
Created at: April 10, 2026, 3:18 a.m.