Triple
T19932834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashington |
E479097
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | PULBOROUGH |
—
|
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: PULBOROUGH | Statement: [Ashington, hasPostTown, PULBOROUGH]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PULBOROUGH Context triple: [Ashington, hasPostTown, PULBOROUGH]
-
A.
Pulborough
chosen
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.
-
B.
Purbrook
Purbrook is a suburban village in Hampshire, England, situated near Portsmouth and forming part of the wider Havant area.
-
C.
Pontesbury
Pontesbury is a large village and civil parish in Shropshire, England, situated southwest of Shrewsbury on the edge of the Shropshire Hills.
-
D.
Popley
Popley is a residential suburb and housing estate in the northern part of Basingstoke, Hampshire, England.
-
E.
Polebrook
Polebrook is a small rural village in Northamptonshire, England, known for its historic church and traditional English countryside setting.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a14a2348190b41f8e320fe661d6 |
completed | April 20, 2026, 4:53 p.m. |
Created at: April 10, 2026, 1:53 p.m.