Triple
T15648946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belaugh |
E376253
|
entity |
| Predicate | nearestTown |
P350
|
FINISHED |
| Object | Wroxham |
E300340
|
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: Wroxham | Statement: [Belaugh, nearestTown, Wroxham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wroxham Context triple: [Belaugh, nearestTown, Wroxham]
-
A.
Wroxham
chosen
Wroxham is a village in Norfolk, England, widely regarded as the main boating and tourist centre of the Norfolk Broads.
-
B.
Wymondham
Wymondham is a historic market town in the English county of Norfolk, known for its medieval abbey and traditional architecture.
-
C.
Thetford
Thetford is a historic market town in eastern England known for its ancient earthworks, links to Thomas Paine, and surrounding Breckland forest.
-
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.
Dereham
Dereham is a market town in the English county of Norfolk, known historically for its agriculture and rural 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ed7212c8190be6ff76afa25f7ca |
completed | April 16, 2026, 2:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff82e921e48190b5b5f4006ad65844 |
completed | May 9, 2026, 6:54 p.m. |
Created at: April 10, 2026, 4:15 a.m.