Triple
T13585667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marlesford |
E324551
|
entity |
| Predicate | nearbyTown |
P3883
|
FINISHED |
| Object | Framlingham |
E299686
|
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: Framlingham | Statement: [Marlesford, nearbyTown, Framlingham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Framlingham Context triple: [Marlesford, nearbyTown, Framlingham]
-
A.
Framlingham
chosen
Framlingham is a historic market town in Suffolk, England, best known for its well-preserved medieval castle.
-
B.
Halesworth
Halesworth is a small historic market town in Suffolk, England, known for its traditional high street and proximity to the Suffolk Coast and Heaths Area of Outstanding Natural Beauty.
-
C.
Aylsham
Aylsham is a historic market town in eastern England known for its traditional architecture and proximity to the Norfolk Broads.
-
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.
Fakenham
Fakenham is a market town in Norfolk, England, known historically for its agriculture and as a local commercial center.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb03310fc819092a56b9f2d73f560 |
completed | April 12, 2026, 2:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78ae1d1b08190ad07b159ac3eba4b |
completed | May 3, 2026, 5:50 p.m. |
Created at: April 9, 2026, 9:49 p.m.