Triple
T12096512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pewsey |
E288083
|
entity |
| Predicate | postTown |
P2711
|
FINISHED |
| Object | PEWSEY |
E288083
|
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: PEWSEY | Statement: [Pewsey, postTown, PEWSEY]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PEWSEY Context triple: [Pewsey, postTown, PEWSEY]
-
A.
Pewsey
chosen
Pewsey is a large village and civil parish in Wiltshire, England, situated in the Vale of Pewsey and known for its rural setting and historic market-town character.
-
B.
Pilsley
Pilsley is a village in Derbyshire, England, known for its rural character and proximity to the Peak District.
-
C.
Vale of Pewsey
The Vale of Pewsey is a broad, fertile valley in Wiltshire, England, known for its chalk downlands, prehistoric sites, and traditional agricultural landscape.
-
D.
Wyre
Wyre is a district and local government area in Lancashire, England, named after the River Wyre and known for its mix of coastal towns and rural countryside.
-
E.
Wyre
Wyre is a small, sparsely populated island in the Orkney archipelago of Scotland, known for its tranquil landscape and archaeological sites.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91552645c81909aff601ab3d3c0e6 |
completed | April 10, 2026, 3:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f6708f8881909c4f40a466bc0acf |
completed | May 2, 2026, 1:04 p.m. |
Created at: April 8, 2026, 9:48 p.m.