Triple
T17690536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rochford |
E441013
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | ROCHFORD |
—
|
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: ROCHFORD | Statement: [Rochford, hasPostTown, ROCHFORD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ROCHFORD Context triple: [Rochford, hasPostTown, ROCHFORD]
-
A.
Rochford
chosen
Rochford is a small town in Essex, England, serving as the administrative center for the surrounding Rochford District.
-
B.
Faversham
Faversham is a historic market town in Kent, England, known for its medieval architecture, maritime heritage, and long-standing brewing industry.
-
C.
Fordwich
Fordwich is a small historic town in Kent, England, often noted as one of the smallest towns in Britain and situated near Canterbury.
-
D.
Wivenhoe
Wivenhoe is a riverside town in Essex, England, known for its historic maritime character, artistic community, and proximity to the University of Essex.
-
E.
Wivenhoe
Wivenhoe is a locality in Queensland, Australia, situated near the Wivenhoe Dam and associated with the broader Sunshine Coast region.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4704b43a88190ba29654ca695839e |
completed | April 19, 2026, 6:03 a.m. |
Created at: April 10, 2026, 10:03 a.m.