Triple
T13616486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Market Weston |
E325326
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Hopton |
E325324
|
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: Hopton | Statement: [Market Weston, locatedNear, Hopton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hopton Context triple: [Market Weston, locatedNear, Hopton]
-
A.
Hopton
chosen
Hopton is a village and civil parish located in the English county of Suffolk.
-
B.
Choppington
Choppington is a village and former mining community in Northumberland, England, situated near the town of Ashington.
-
C.
Rolphton
Rolphton is a small community in the town of Laurentian Hills in Renfrew County, Ontario, Canada, historically associated with early nuclear research at the nearby Chalk River Laboratories.
-
D.
Yapton
Yapton is a village and civil parish in West Sussex, England, situated near the south coast between Bognor Regis and Littlehampton.
-
E.
Hartsop
Hartsop is a small, traditional Lakeland village in the English Lake District, known for its stone cottages and scenic valley setting near Ullswater.
- 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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb0ad0a7c81909c7972187202db96 |
completed | April 12, 2026, 2:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78ae7d6908190836172e955b0d7e8 |
completed | May 3, 2026, 5:50 p.m. |
Created at: April 9, 2026, 9:50 p.m.