Triple
T11193577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seacombe |
E264863
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Poulton |
E375758
|
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: Poulton | Statement: [Seacombe, adjacentTo, Poulton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Poulton Context triple: [Seacombe, adjacentTo, Poulton]
-
A.
Workington
Workington is a coastal town and port on the west coast of England, historically known for its steel and coal industries and situated at the mouth of the River Derwent.
-
B.
Wooler
Wooler is a small market town and gateway to the Cheviot Hills in northern England.
-
C.
Pilton
Pilton is a historic suburb and former village now forming part of the town of Barnstaple in North Devon, England.
-
D.
Pilton
Pilton is a residential district in the north of Edinburgh, Scotland, known for its large housing estates and proximity to Granton.
-
E.
Prenton
chosen
Prenton is a suburban residential area on the Wirral Peninsula in Merseyside, England, known for its parks, schools, and proximity to Birkenhead.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8be025481909d311b587418dfb2 |
completed | April 9, 2026, 5:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e483f8ecf4819086f0bab3ca9ddcb4 |
completed | April 19, 2026, 7:27 a.m. |
Created at: April 8, 2026, 9:29 p.m.