Triple
T14021672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Peter and St Paul, Chaldon |
E337346
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Chaldon |
E337346
|
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: Chaldon | Statement: [St Peter and St Paul, Chaldon, locatedIn, Chaldon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chaldon Context triple: [St Peter and St Paul, Chaldon, locatedIn, Chaldon]
-
A.
Chaldon
chosen
Chaldon is a small historic village in Surrey, England, noted for its ancient church and rural character within the Tandridge district.
-
B.
Claydon
Claydon is a village and civil parish located in the county of Suffolk in eastern England.
-
C.
Claydon
Claydon is a small village in Buckinghamshire, England, known for its rural setting and proximity to historic railway sites.
-
D.
Windlestone
Windlestone is a village in County Durham, England, known for its historic country house, Windlestone Hall, and its rural surroundings.
-
E.
Kilndown
Kilndown is a small rural village in Kent, England, known for its historic church and woodland 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f3c7cd88190b236382058581740 |
completed | April 14, 2026, 12:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fbc32f78dc8190bd357d179cbaa5bc |
completed | May 6, 2026, 10:39 p.m. |
Created at: April 9, 2026, 10:19 p.m.