Triple
T6252745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lancing |
E140086
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Sompting |
E490429
|
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: Sompting | Statement: [Lancing, adjacentTo, Sompting]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sompting Context triple: [Lancing, adjacentTo, Sompting]
-
A.
Sompting
chosen
Sompting is a village and civil parish in West Sussex, England, situated near the south coast between Worthing and Lancing.
-
B.
Cullompton
Cullompton is a historic market town in Devon, England, known for its agricultural heritage and location in the Culm Valley.
-
C.
Bramshott
Bramshott is a historic village in Hampshire, England, known for its picturesque countryside and association with nearby heathland areas.
-
D.
Shrivenham
Shrivenham is a village in Oxfordshire, England, known for its historic high street, rural setting, and association with nearby military and academic institutions.
-
E.
Okehampton
Okehampton is a historic market town in Devon, England, known for its medieval castle and role as a former parliamentary borough.
- 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_69c008b4858c819095b0199114a9a87b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063417c8c8190945049881819d307 |
completed | March 22, 2026, 9:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c2442a556081908b91e7d999a82514 |
completed | March 24, 2026, 7:58 a.m. |
Created at: March 22, 2026, 4:24 p.m.