Triple
T12806796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Bersted |
E306163
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | North Bersted |
E303941
|
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: North Bersted | Statement: [South Bersted, adjacentTo, North Bersted]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: North Bersted Context triple: [South Bersted, adjacentTo, North Bersted]
-
A.
North Bersted
chosen
North Bersted is a residential suburb and parish area on the outskirts of Bognor Regis in West Sussex, England.
-
B.
South Bersted
South Bersted is a residential area and suburb forming part of the seaside town of Bognor Regis on the south coast of England.
-
C.
Binsted
Binsted is a rural civil parish and village in East Hampshire, England, known for its countryside setting and historic church.
-
D.
Binsted
Binsted is a small rural village in West Sussex, England, known for its historic parish church of the Holy Cross and its surrounding countryside.
-
E.
Blangsted
Blangsted is a surname most notably associated with Folmar Blangsted, a film editor.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e7f370c8190b3fc39c1b63394c6 |
completed | April 10, 2026, 9:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f68ec6556081909375fada79ddcb8c |
completed | May 2, 2026, 11:54 p.m. |
Created at: April 9, 2026, 5:31 p.m.