Triple
T7649592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thropton |
E173213
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | Morpeth |
E166285
|
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: Morpeth | Statement: [Thropton, hasPostTown, Morpeth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Morpeth Context triple: [Thropton, hasPostTown, Morpeth]
-
A.
Morpeth
chosen
Morpeth is a historic market town in Northumberland, England, known for its traditional architecture and role as a local commercial and administrative centre.
-
B.
Didlington
Didlington is a small village in Norfolk, England, known for its rural landscape, historic estate, and proximity to the River Wissey.
-
C.
Hexham
Hexham is a historic market town in Northumberland, England, known for its medieval abbey and proximity to Hadrian’s Wall.
-
D.
Benwell
Benwell is a residential district in the west end of Newcastle upon Tyne, England, known for its historical industrial roots and subsequent urban regeneration.
-
E.
Cramlington
Cramlington is a modern, largely residential town in North East England known for its post-war development and proximity to Newcastle upon Tyne.
- 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_69c6995473348190a4f41d110d619a18 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70174af248190af6695e127776c02 |
completed | March 27, 2026, 10:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8d69adda4819087ca9eb631e0de54 |
completed | March 29, 2026, 7:36 a.m. |
Created at: March 27, 2026, 3:58 p.m.