Triple
T7393402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashford, Surrey |
E170557
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Laleham |
E176096
|
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: Laleham | Statement: [Ashford, Surrey, locatedNear, Laleham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Laleham Context triple: [Ashford, Surrey, locatedNear, Laleham]
-
A.
Laleham
chosen
Laleham is a riverside village in Surrey, England, situated on the River Thames and known for its historic church, green spaces, and residential character.
-
B.
Hellingly
Hellingly is a village and civil parish in East Sussex, England, known for its rural character and historic parish church.
-
C.
Lastingham
Lastingham is a small historic village in North Yorkshire, England, noted for its ancient church and tranquil setting on the edge of the North York Moors.
-
D.
Harrodstown
Harrodstown was the original pioneer settlement that later became Harrodsburg, recognized as one of the earliest permanent European-American communities in Kentucky.
-
E.
Bookham
Bookham is a village in Surrey, England, known for its residential character and proximity to the North Downs countryside.
- 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_69c68a5e2c9081909e713ce866e0060a |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2263b48819089319a2a2f0d3357 |
completed | March 27, 2026, 9:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c810f82ba08190919924b0994a2eee |
completed | March 28, 2026, 5:33 p.m. |
Created at: March 27, 2026, 3:09 p.m.