Triple
T5393083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borough of Waverley |
E120581
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Tilford |
E436986
|
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: Tilford | Statement: [Borough of Waverley, containsSettlement, Tilford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tilford Context triple: [Borough of Waverley, containsSettlement, Tilford]
-
A.
Tilford
chosen
Tilford is a village in Surrey, England, notable as the location of the international headquarters of the Ahmadiyya Muslim Community.
-
B.
Twyford
Twyford is a village and civil parish in Berkshire, England, known as a commuter settlement between Reading and London.
-
C.
Ashtead
Ashtead is a large suburban village in Surrey, England, known for its residential character, local amenities, and proximity to the town of Leatherhead.
-
D.
Tilbrook
Tilbrook is a small rural village and civil parish in Cambridgeshire, England, situated near the historic town of Kimbolton.
-
E.
Pyrford
Pyrford is a village in Surrey, England, known for its historic church, green spaces, and residential character near the town of Woking.
- 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_69bf336d43a081909ab05d237c297c7b |
completed | March 22, 2026, 12:10 a.m. |
Created at: March 20, 2026, 2:04 p.m.