Triple
T14700158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Costessey |
E345273
|
entity |
| Predicate | hasNearbySettlement |
P4647
|
FINISHED |
| Object | Taverham |
E346473
|
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: Taverham | Statement: [Costessey, hasNearbySettlement, Taverham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Taverham Context triple: [Costessey, hasNearbySettlement, Taverham]
-
A.
Taverham
chosen
Taverham is a village and civil parish in Norfolk, England, situated near the city of Norwich along the River Wensum.
-
B.
Thornham
Thornham is a coastal village in Norfolk, England, known for its salt marshes, sandy beaches, and traditional rural character.
-
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.
Stalham
Stalham is a small market town in Norfolk, England, known as a gateway to 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb605f5948190ab6b20887c4b6833 |
completed | April 14, 2026, 9:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fde191ef6081908434db8d89ad38cb |
completed | May 8, 2026, 1:13 p.m. |
Created at: April 10, 2026, 1:28 a.m.