Triple
T7250970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reedham |
E157598
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | NORWICH |
E41722
|
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: NORWICH | Statement: [Reedham, hasPostTown, NORWICH]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NORWICH Context triple: [Reedham, hasPostTown, NORWICH]
-
A.
Norwich
chosen
Norwich is a historic cathedral city in Norfolk, England, known for its medieval architecture and role as a regional cultural and economic center.
-
B.
Norwich
Norwich is a rural township in Oxford County, Ontario, known for its agricultural community and small-town character.
-
C.
Ipswich
Ipswich is a historic town and port in Suffolk, England, known as one of the country’s oldest continuously inhabited settlements.
-
D.
Ipswich
Ipswich is a historic city in South East Queensland, Australia, known for its heritage architecture and role as a major residential and industrial hub west of Brisbane.
-
E.
Norwich–Cambridge
Norwich–Cambridge is a regional passenger rail service in eastern England linking the city of Norwich with Cambridge.
- 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_69c6882d81d4819085f7ff862951ee4f |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea791fec8190aee56ab4503770be |
completed | March 27, 2026, 8:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7e523149481909bbc7dd88046e8b0 |
completed | March 28, 2026, 2:26 p.m. |
Created at: March 27, 2026, 2:56 p.m.