Triple
T16016586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sefton village |
E388481
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Litherland |
E90878
|
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: Litherland | Statement: [Sefton village, locatedNear, Litherland]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Litherland Context triple: [Sefton village, locatedNear, Litherland]
-
A.
Litherland
chosen
Litherland is a suburban town in Merseyside, England, situated to the north of Liverpool within its wider urban area.
-
B.
Leylands
Leylands is a residential neighbourhood within the town of Burgess Hill in West Sussex, England.
-
C.
Heswall
Heswall is a town on the Wirral Peninsula in Merseyside, England, known for its residential character, golf courses, and views over the Dee Estuary toward North Wales.
-
D.
Skelmersdale
Skelmersdale is a planned new town in West Lancashire, England, known for its extensive roundabout road system and post-war housing developments.
-
E.
Levenshulme
Levenshulme is a residential suburb in south Manchester, England, known for its diverse community and vibrant local markets.
- 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_69d86dabcb7c8190b6a39d6831d2fa1b |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e18294f6c48190ab9d3eead268f846 |
completed | April 17, 2026, 12:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffe470cd5881909cc0c48b3a540d61 |
completed | May 10, 2026, 1:50 a.m. |
Created at: April 10, 2026, 4:55 a.m.