Triple
T19933126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horsham District Council |
E479105
|
entity |
| Predicate | hasJurisdictionOver |
P808
|
FINISHED |
| Object | Henfield |
—
|
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: Henfield | Statement: [Horsham District Council, hasJurisdictionOver, Henfield]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Henfield Context triple: [Horsham District Council, hasJurisdictionOver, Henfield]
-
A.
Henfield
chosen
Henfield is a large historic village and civil parish in the Horsham District of West Sussex, England, known for its rural character and community amenities.
-
B.
Henleyfield
Henleyfield is a small unincorporated community located in Pearl River County in southern Mississippi, United States.
-
C.
Austerfield
Austerfield is a small village in South Yorkshire, England, notable for its historic church and connections to early English history.
-
D.
Henbury
Henbury is a small settlement within the civil parish of Sturminster Marshall in Dorset, England.
-
E.
Ninfield
Ninfield is a small rural village and civil parish in East Sussex, England, known for its countryside setting and historic character.
- 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_69e65a1553348190a6c4004d3f9a57c5 |
completed | April 20, 2026, 4:53 p.m. |
Created at: April 10, 2026, 1:53 p.m.