Triple
T18827315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarporley |
E460422
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | Tarporley |
—
|
NE NERFINISHED |
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: Tarporley | Statement: [Tarporley, hasPostTown, Tarporley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tarporley Context triple: [Tarporley, hasPostTown, Tarporley]
-
A.
Tarporley
chosen
Tarporley is a picturesque village and civil parish in Cheshire, England, known for its historic high street, traditional pubs, and rural charm.
-
B.
Mossley
Mossley is a small town in Greater Manchester, England, situated in the Tame Valley between Manchester and Huddersfield.
-
C.
Tyldesley
Tyldesley is a town in Greater Manchester, England, historically part of Lancashire and known for its industrial heritage, particularly in coal mining and textiles.
-
D.
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.
-
E.
Peterlee
Peterlee is a post-war new town in North East England, established to serve nearby coal mining communities.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a6bfa4a88190b17d3118121414be |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 10, 2026, 11:56 a.m.