Triple
T11094157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M&GN Joint Railway |
E262331
|
entity |
| Predicate | servedTown |
P3936
|
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: [M&GN Joint Railway, servedTown, Norwich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Norwich Context triple: [M&GN Joint Railway, servedTown, 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.
Lowestoft
Lowestoft is a coastal town in Suffolk, England, known as the easternmost settlement in the United Kingdom and a traditional fishing and seaside resort.
-
D.
King's Lynn
King's Lynn is a historic market and port town in Norfolk, England, known for its medieval architecture and long-standing role as a regional commercial center.
-
E.
Northampton
Northampton is a historic market town and the county town of Northamptonshire in the East Midlands of England.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a0783e88190aae3d461730c2d70 |
completed | April 9, 2026, 12:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e42d69c8b4819092614e83e855430e |
completed | April 19, 2026, 1:18 a.m. |
Created at: April 8, 2026, 9:27 p.m.