Triple
T23083656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cullompton |
E575543
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | CULLompton |
E575543
|
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: CULLompton | Statement: [Cullompton, hasPostTown, CULLompton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CULLompton Context triple: [Cullompton, hasPostTown, CULLompton]
-
A.
Cullompton
chosen
Cullompton is a historic market town in Devon, England, known for its agricultural heritage and location in the Culm Valley.
-
B.
Chilcompton
Chilcompton is a rural village in Somerset, England, known for its historic character and location near the town of Midsomer Norton.
-
C.
Beaminster
Beaminster is a small historic market town in Dorset, England, known for its picturesque countryside setting and traditional architecture.
-
D.
Warminster
Warminster is a market town in Wiltshire, England, known for its historic architecture, surrounding countryside, and role as a local transport and service hub.
-
E.
Warminster
Warminster is a suburban township in Bucks County, Pennsylvania, known for its residential communities, local commerce, and small general-aviation airport.
- 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_69e245bf3e3c819086d3448720efc01b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18da304548190ab7a421c1ded0eb6 |
completed | April 29, 2026, 4:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0c15b27e24819098404554c6097105 |
completed | May 19, 2026, 7:48 a.m. |
Created at: April 17, 2026, 3:56 p.m.