Triple
T9530444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PE postcode area |
E229875
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | Swaffham |
E164461
|
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: Swaffham | Statement: [PE postcode area, hasPostTown, Swaffham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Swaffham Context triple: [PE postcode area, hasPostTown, Swaffham]
-
A.
Swaffham
chosen
Swaffham is a historic market town in the English county of Norfolk, known for its traditional town center and surrounding rural landscape.
-
B.
Swaffham Bulbeck
Swaffham Bulbeck is a rural village and civil parish in Cambridgeshire, England, known for its historic church, traditional architecture, and agricultural surroundings.
-
C.
Fakenham
Fakenham is a market town in Norfolk, England, known historically for its agriculture and as a local commercial center.
-
D.
Paglesham
Paglesham is a small rural village in Essex, England, known historically for its fishing, boatbuilding, and smuggling heritage along the River Roach.
-
E.
Wroxham
Wroxham is a village in Norfolk, England, widely regarded as the main boating and tourist centre of the Norfolk Broads.
- 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_69ca8479934c81908006d0e6e970ae05 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98b2de3081909be70d9ab187dce6 |
completed | April 1, 2026, 10:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d14c38a3848190ab3561f70497c9eb |
completed | April 4, 2026, 5:36 p.m. |
Created at: March 30, 2026, 8 p.m.