Triple
T6329373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Molesey |
E141939
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | Molesey |
E25826
|
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: Molesey | Statement: [West Molesey, partOf, Molesey]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Molesey Context triple: [West Molesey, partOf, Molesey]
-
A.
Molesey
chosen
Molesey is a suburban town in south-east England situated on the River Thames, known for its proximity to Hampton Court Palace and its residential character within the London commuter belt.
-
B.
Biddenden
Biddenden is a historic village in Kent, England, known for its traditional Wealden architecture, vineyards, and the local legend of the Biddenden Maids.
-
C.
Hellingly
Hellingly is a village and civil parish in East Sussex, England, known for its rural character and historic parish church.
-
D.
Willingdon
Willingdon is a village in East Sussex, England, situated near the town of Hailsham.
-
E.
Gamesley
Gamesley is a residential area and former council estate on the outskirts of Glossop in Derbyshire, England.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0651334c08190a9514faa36e7812d |
completed | March 22, 2026, 9:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c63862698c8190a23f9f228a7cc8a7 |
completed | March 27, 2026, 7:57 a.m. |
Created at: March 22, 2026, 4:30 p.m.