Triple
T5812769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arun District |
E128909
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Felpham |
E304588
|
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: Felpham | Statement: [Arun District, hasTown, Felpham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Felpham Context triple: [Arun District, hasTown, Felpham]
-
A.
Felpham
chosen
Felpham is a coastal village and residential suburb on the south coast of England, situated just east of Bognor Regis in West Sussex.
-
B.
Padiham
Padiham is a small town in Lancashire, England, situated near Burnley and known for its industrial heritage and proximity to the River Calder.
-
C.
Bramford
Bramford is a village and civil parish located near Ipswich in the county of Suffolk, England.
-
D.
Greatham
Greatham is a small village and civil parish in the East Hampshire district of Hampshire, England, known for its rural character and proximity to the A3 road.
-
E.
Pendlebury
Pendlebury is a suburban area in the City of Salford, Greater Manchester, England, historically known for its coal mining and textile industries.
- 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_69c0084788848190bcf71f6bc5d71597 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b56044c8190847478a342d441c2 |
completed | March 22, 2026, 5:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c09848dd148190aeea1b1d454b8da5 |
completed | March 23, 2026, 1:32 a.m. |
Created at: March 22, 2026, 3:52 p.m.