Triple
T15258920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heswall |
E364719
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Pensby |
E1057736
|
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: Pensby | Statement: [Heswall, locatedNear, Pensby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pensby Context triple: [Heswall, locatedNear, Pensby]
-
A.
Pensby
chosen
Pensby is a suburban village on the Wirral Peninsula in Merseyside, England.
-
B.
Navenby
Navenby is a historic village and civil parish in Lincolnshire, England, known for its traditional architecture and rural character.
-
C.
Pendlebury
Pendlebury is a suburban area in the City of Salford, Greater Manchester, England, historically known for its coal mining and textile industries.
-
D.
Hunsonby
Hunsonby is a small rural village and civil parish in Cumbria, England, situated in the Eden Valley near the town of Penrith.
-
E.
Tealby
Tealby is a picturesque rural village in eastern England, known for its traditional stone cottages and scenic setting within the Lincolnshire 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0084d11148190919eef8e55569bb9 |
completed | April 15, 2026, 9:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fee5f9a0708190bc429692788a63d7 |
completed | May 9, 2026, 7:44 a.m. |
Created at: April 10, 2026, 3:13 a.m.