Triple
T9746212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warlingham |
E236314
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Caterham |
E24541
|
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: Caterham | Statement: [Warlingham, near, Caterham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Caterham Context triple: [Warlingham, near, Caterham]
-
A.
Caterham
chosen
Caterham is a town in the Tandridge district of Surrey, England, known as a commuter settlement on the edge of the London metropolitan area.
-
B.
Caterham-on-the-Hill
Caterham-on-the-Hill is a residential town in Surrey, England, known for its elevated position above Caterham Valley and its mix of historic and modern suburban development.
-
C.
Cheveley
Cheveley is a small rural village and civil parish in eastern England, known for its historic church and proximity to the horse-racing town of Newmarket.
-
D.
Cobham
Cobham is a historic village in north-west Kent, England, known for its traditional architecture, surrounding countryside, and notable landmarks such as Cobham Hall.
-
E.
Cobham
Cobham is a village in Surrey, England, known for its affluent residential character, proximity to London, and scenic riverside setting.
- 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_69ca84d3e24481908a476e2231123cf9 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9f65ad788190b68d731b6f516d93 |
completed | April 1, 2026, 10:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1b004a6e88190a974f4a8973f91ef |
completed | April 5, 2026, 12:42 a.m. |
Created at: March 30, 2026, 8:23 p.m.