Triple
T7236289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steyning |
E155235
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Bramber |
E191285
|
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: Bramber | Statement: [Steyning, near, Bramber]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bramber Context triple: [Steyning, near, Bramber]
-
A.
Bramber
chosen
Bramber is a historic village in West Sussex, England, known for the ruins of Bramber Castle and its picturesque rural setting.
-
B.
Amberley
Amberley is a picturesque village in West Sussex, England, known for its historic cottages, castle, and scenic setting in the South Downs near the River Arun.
-
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.
Bookham
Bookham is a village in Surrey, England, known for its residential character and proximity to the North Downs countryside.
- 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_69c688143bfc81908d4176617735e601 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea33dd3481908ebb050e1fab5aaa |
completed | March 27, 2026, 8:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7cc32d6c48190ae78b3d1227bb868 |
completed | March 28, 2026, 12:40 p.m. |
Created at: March 27, 2026, 2:55 p.m.