Triple
T17006073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Anne’s Church, Baslow |
E412573
|
entity |
| Predicate | parish |
P2739
|
FINISHED |
| Object | Baslow |
E412574
|
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: Baslow | Statement: [St Anne’s Church, Baslow, parish, Baslow]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Baslow Context triple: [St Anne’s Church, Baslow, parish, Baslow]
-
A.
Baslow
chosen
Baslow is a village in Derbyshire, England, situated near Chatsworth House in the Peak District and known for its picturesque setting and historic parish church.
-
B.
Vanselow
Vanselow is a German-language surname borne by various individuals, including figures such as Ernst Vanselow.
-
C.
Shklow
Shklow is a town in eastern Belarus known for its historical significance and location along the Dnieper River in the Mogilev Region.
-
D.
Halanzy
Halanzy is a village in the municipality of Aubange in the province of Luxembourg, Belgium.
-
E.
Tadlow
Tadlow is a small rural village in the county of Cambridgeshire in eastern England, known for its historic church and agricultural surroundings.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d3831268819089286053a5acf653 |
completed | April 18, 2026, 6:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01233134288190bbe151f257150dfb |
completed | May 11, 2026, 12:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.