Triple
T20498015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selsey Bill |
E503223
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Selsey |
—
|
NE NERFINISHED |
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: Selsey | Statement: [Selsey Bill, locatedIn, Selsey]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Selsey Context triple: [Selsey Bill, locatedIn, Selsey]
-
A.
Selsey
chosen
Selsey is a coastal town in West Sussex, England, historically notable as the original seat of the Anglo-Saxon bishops of the Kingdom of Sussex before the see moved to Chichester.
-
B.
Yateley
Yateley is a small town in northeast Hampshire, England, known for its residential character, local schools, and nearby lakes and heathland.
-
C.
Haslemere
Haslemere is a historic market town in the southwest of Surrey, England, near the borders with Hampshire and West Sussex.
-
D.
Pulborough
Pulborough is a large rural village and civil parish in the Arun district of West Sussex, England, known for its position on the River Arun and proximity to the South Downs.
-
E.
Uckfield
Uckfield is a small market town in East Sussex, England, known for its historic high street and role as a local commercial and commuter hub.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4b1e52c8190894281cf7e3283ab |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69cbefe4c819098af5bfd4d92341d |
completed | April 20, 2026, 9:38 p.m. |
Created at: April 16, 2026, 11:35 a.m.