Triple
T2801757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suffolk, England |
E53163
|
entity |
| Predicate | hasNotableTown |
P14082
|
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: [Suffolk, England, hasNotableTown, Lavenham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lavenham Context triple: [Suffolk, England, hasNotableTown, 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.
Wroxham
Wroxham is a village in Norfolk, England, widely regarded as the main boating and tourist centre of the Norfolk Broads.
-
D.
Boxford
Boxford is a village and civil parish in Suffolk, England, known for its historic buildings and rural character.
-
E.
Mendlesham
Mendlesham is a rural village and civil parish in Suffolk, England, known for its historic church and traditional village character.
- 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abde1117148190b0c98f906f1c872e |
completed | March 7, 2026, 8:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b055cd4e1c8190a2eb97e648aa0080 |
completed | March 10, 2026, 5:33 p.m. |
Created at: March 6, 2026, 9:58 p.m.