Triple
T9640795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Littleton |
E233058
|
entity |
| Predicate | nearbySettlement |
P350
|
FINISHED |
| Object | Shepperton Green |
E762498
|
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: Shepperton Green | Statement: [Littleton, nearbySettlement, Shepperton Green]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shepperton Green Context triple: [Littleton, nearbySettlement, Shepperton Green]
-
A.
Shepperton Green
chosen
Shepperton Green is a small residential locality in Shepperton, Surrey, England, known for its village green and proximity to the River Thames.
-
B.
Wooburn Green
Wooburn Green is a village and large green in Buckinghamshire, England, situated near High Wycombe in the River Wye valley.
-
C.
Talbot Green
Talbot Green is a retail and commercial village in Rhondda Cynon Taf, South Wales, known for its shopping centre and role as a local economic hub.
-
D.
Englefield Green
Englefield Green is a village in Surrey, England, known for its proximity to Runnymede and its large common land.
-
E.
Esher Green
Esher Green is a historic village green and open space in Esher, Surrey, known for its picturesque setting and local recreational use.
- 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_69ca848a5a908190aad251f4137b0c3a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b552a1c81909a1fab347110eeb1 |
completed | April 1, 2026, 10:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d189fd53fc8190bc36f2b8e0e21036 |
completed | April 4, 2026, 10 p.m. |
Created at: March 30, 2026, 8:12 p.m.