Triple
T12535676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sudbury |
E299682
|
entity |
| Predicate | hasNeighbouringTown |
P3883
|
FINISHED |
| Object | Great Cornard |
E299703
|
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: Great Cornard | Statement: [Sudbury, hasNeighbouringTown, Great Cornard]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Great Cornard Context triple: [Sudbury, hasNeighbouringTown, Great Cornard]
-
A.
Great Cornard
chosen
Great Cornard is a large village and civil parish situated near Sudbury in the county of Suffolk, England.
-
B.
Denmead
Denmead is a large village and civil parish in Hampshire, England, situated near Waterlooville and on the edge of the South Downs.
-
C.
Grindon
Grindon is a residential suburb of Sunderland in the Wearside area of North East England.
-
D.
Mittelhaardt
Mittelhaardt is a renowned wine-growing area within Germany’s Palatinate (Pfalz) region, noted especially for its high-quality Riesling vineyards.
-
E.
Quarndon
Quarndon is a small village and civil parish in Derbyshire, England, situated just north of the city of Derby.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d9546d3b2081908d3e0659f8f13678 |
completed | April 10, 2026, 7:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6557a95d48190ac588807544f060f |
completed | May 2, 2026, 7:50 p.m. |
Created at: April 8, 2026, 9:57 p.m.