Triple
T11779272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halnaker Windmill |
E280098
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Halnaker |
E280098
|
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: Halnaker | Statement: [Halnaker Windmill, locatedIn, Halnaker]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Halnaker Context triple: [Halnaker Windmill, locatedIn, Halnaker]
-
A.
Halnaker
chosen
Halnaker is a small village in West Sussex, England, known for its historic windmill and picturesque countryside near the South Downs.
-
B.
Hanborough
Hanborough is a civil parish in West Oxfordshire, England, encompassing the villages of Long Hanborough and Church Hanborough.
-
C.
Hellingly
Hellingly is a village and civil parish in East Sussex, England, known for its rural character and historic parish church.
-
D.
Baverstock
Baverstock is a small rural hamlet in Wiltshire, England, known for its historic church and tranquil countryside setting.
-
E.
Harnham
Harnham is a suburb of Salisbury in Wiltshire, England, known for its historic buildings and scenic riverside setting near Salisbury Cathedral.
- 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_69d6ab01d2688190ad8ed6bda487eaa5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a5623f708190a18aea570577a3f6 |
completed | April 10, 2026, 7:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f090b8f4c481908cb3cf03875c0e24 |
completed | April 28, 2026, 10:49 a.m. |
Created at: April 8, 2026, 9:42 p.m.