Triple
T17891840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thamesdown district |
E447336
|
entity |
| Predicate | containedSettlement |
P16159
|
FINISHED |
| Object | Highworth |
—
|
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: Highworth | Statement: [Thamesdown district, containedSettlement, Highworth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Highworth Context triple: [Thamesdown district, containedSettlement, Highworth]
-
A.
Highworth
chosen
Highworth is a historic market town in Wiltshire, England, known for its elevated position and traditional architecture.
-
B.
Nailsworth
Nailsworth is a small market town in Gloucestershire, England, known for its Cotswold setting and independent shops and eateries.
-
C.
Northaw
Northaw is a village and civil parish in southern England, known for its rural character and location within the county of Hertfordshire.
-
D.
Brinkworth
Brinkworth is a rural village and civil parish in Wiltshire, England, noted for its long, linear layout and historic buildings.
-
E.
Rushworth
Rushworth is the middle name of Lord Jellicoe, a British naval officer and statesman who served as First Sea Lord during World War I.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49d7a855c8190b20bdbf6dcd4fd47 |
completed | April 19, 2026, 9:16 a.m. |
Created at: April 10, 2026, 10:19 a.m.