Triple
T6302987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petworth |
E141299
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Midhurst |
E166978
|
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: Midhurst | Statement: [Petworth, near, Midhurst]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Midhurst Context triple: [Petworth, near, Midhurst]
-
A.
Midhurst
Midhurst is a small community in Ontario, Canada, serving as the administrative center for Simcoe County.
-
B.
Midhurst
chosen
Midhurst is a historic market town in South East England known for its picturesque streets, Tudor buildings, and proximity to the South Downs National Park.
-
C.
Highworth
Highworth is a historic market town in Wiltshire, England, known for its elevated position and traditional architecture.
-
D.
Wadhurst
Wadhurst is a rural village in East Sussex, England, known for its historic High Street, surrounding Wealden countryside, and role as a commuter community for nearby towns and London.
-
E.
Crowhurst
Crowhurst is a small rural village and civil parish in Surrey, England, known for its historic church and countryside setting.
- 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_69c008cf0ad4819095def81e2bd42f9f |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0645e150881908b49a07914dcbfd8 |
completed | March 22, 2026, 9:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c5e436e7ec8190a5ea470eb83ddaea |
completed | March 27, 2026, 1:58 a.m. |
Created at: March 22, 2026, 4:27 p.m.