Triple
T5393073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borough of Waverley |
E120581
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Godalming |
E24118
|
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: Godalming | Statement: [Borough of Waverley, containsSettlement, Godalming]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Godalming Context triple: [Borough of Waverley, containsSettlement, Godalming]
-
A.
Godalming
chosen
Godalming is a historic market town in southeast England known for its picturesque streets, riverside setting, and role as a commuter hub for London.
-
B.
Oakengates
Oakengates is a small town in Shropshire, England, now effectively part of the Telford urban area.
-
C.
Gamesley
Gamesley is a residential area and former council estate on the outskirts of Glossop in Derbyshire, England.
-
D.
Ingatestone
Ingatestone is a historic village and civil parish in southeast England known for its traditional architecture and commuter links to London.
-
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_69bd4637b92c8190b815b6443ae4b323 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd871b81d08190993928e2c6251226 |
completed | March 20, 2026, 5:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf3a9b9ff881908edc10f29f62df1c |
completed | March 22, 2026, 12:40 a.m. |
Created at: March 20, 2026, 2:04 p.m.