Triple
T9195538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hersham |
E220696
|
entity |
| Predicate | locatedNear |
P294
|
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: [Hersham, locatedNear, Molesey]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Molesey Context triple: [Hersham, locatedNear, 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.
Moorfield
Moorfield is a given name most notably borne by Moorfield Storey, an American lawyer and civil rights leader who served as the first president of the NAACP.
-
C.
Biddenden
Biddenden is a historic village in Kent, England, known for its traditional Wealden architecture, vineyards, and the local legend of the Biddenden Maids.
-
D.
Hellingly
Hellingly is a village and civil parish in East Sussex, England, known for its rural character and historic parish church.
-
E.
Willingdon
Willingdon is a village in East Sussex, England, situated near the town of Hailsham.
- 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_69ca83e7ba70819088b74866d9da2c30 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd87c3a3c8190b60f19873ef6e1f8 |
completed | April 1, 2026, 8:34 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d05c36d7208190a593923bad3d18e7 |
completed | April 4, 2026, 12:32 a.m. |
Created at: March 30, 2026, 7:25 p.m.