Triple
T12539601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lavenham Guildhall |
E299801
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Lavenham |
E301423
|
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: Lavenham | Statement: [Lavenham Guildhall, location, Lavenham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lavenham Context triple: [Lavenham Guildhall, location, Lavenham]
-
A.
Lavenham
chosen
Lavenham is a historic medieval wool town in Suffolk, England, renowned for its well-preserved timber-framed buildings and picturesque streets.
-
B.
Hadleigh
Hadleigh is a historic market town in Suffolk, England, known for its medieval buildings and traditional rural character.
-
C.
Hadleigh
Hadleigh is a town in Essex, England, known for its historic castle ruins and position within the borough of Castle Point.
-
D.
Wroxham
Wroxham is a village in Norfolk, England, widely regarded as the main boating and tourist centre of the Norfolk Broads.
-
E.
Wenham
Wenham is an English-origin surname borne by various notable individuals, including Australian actor David Wenham.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d9546fc620819093335988dbab3256 |
completed | April 10, 2026, 7:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6557cb180819083ee10708320199e |
completed | May 2, 2026, 7:50 p.m. |
Created at: April 8, 2026, 9:57 p.m.