Triple
T8003635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pulborough |
E186311
|
entity |
| Predicate | postTown |
P2711
|
FINISHED |
| Object | PULBOROUGH |
E186311
|
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: PULBOROUGH | Statement: [Pulborough, postTown, PULBOROUGH]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PULBOROUGH Context triple: [Pulborough, postTown, 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.
Popley
Popley is a residential suburb and housing estate in the northern part of Basingstoke, Hampshire, England.
-
C.
Pepperellborough
Pepperellborough was the original name of what is now the city of Saco in Maine, a historic New England mill town in the United States.
-
D.
Pilsley
Pilsley is a village in Derbyshire, England, known for its rural character and proximity to the Peak District.
-
E.
Pocklington
Pocklington is a small market town in the East Riding of Yorkshire, England, known for its historic architecture and surrounding Wolds 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3cf443e48190ac9e83343ff4019e |
completed | March 31, 2026, 3:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cbe121b0ac81908b9da58cf14c8df5 |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 5:18 p.m.