Triple
T8647435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laughton, Sussex |
E205012
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Ringmer |
E47838
|
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: Ringmer | Statement: [Laughton, Sussex, locatedNear, Ringmer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ringmer Context triple: [Laughton, Sussex, locatedNear, Ringmer]
-
A.
Ringmer
chosen
Ringmer is a village and civil parish in East Sussex, England, known in part as the place where former UK Prime Minister James Callaghan died.
-
B.
Brockham
Brockham is a picturesque village in Surrey, England, known for its traditional village green and historic rural character.
-
C.
Rendham
Rendham is a small rural village and civil parish located in the county of Suffolk in eastern England.
-
D.
Humbermede
Humbermede is a residential neighbourhood in the northwestern part of Toronto, Ontario, known for its diverse community and proximity to the Humber River.
-
E.
Rother
Rother is a local government district in East Sussex, England, known for its mix of historic towns, rural landscapes, and coastal areas.
- 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_69ca834e56848190abb0eeaec9dedd32 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc48112b4881908901214f41b6bf71 |
completed | March 31, 2026, 10:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ceccb8b91881908630f3e4c4461af4 |
completed | April 2, 2026, 8:08 p.m. |
Created at: March 30, 2026, 6:29 p.m.