Triple
T10665376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midgham |
E251342
|
entity |
| Predicate | hasNeighbouringSettlement |
P4647
|
FINISHED |
| Object | Aldermaston |
E71399
|
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: Aldermaston | Statement: [Midgham, hasNeighbouringSettlement, Aldermaston]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aldermaston Context triple: [Midgham, hasNeighbouringSettlement, Aldermaston]
-
A.
Aldermaston
chosen
Aldermaston is an English village in Berkshire best known as the site of major anti-nuclear weapons protests and marches.
-
B.
Amersham
Amersham is a historic market town in southeast England known for its picturesque old town, Chilterns countryside setting, and role as a commuter hub into London.
-
C.
Burnham Norton
Burnham Norton is a small coastal village in Norfolk, England, known for its historic church and saltmarsh landscape near the North Sea.
-
D.
Chobham
Chobham is a village and civil parish in Surrey, England, known for its rural character, common land, and historic buildings.
-
E.
Willingdon
Willingdon is a village in East Sussex, England, situated near the town of Hailsham.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6f31f87748190bb44db8afa901763 |
completed | April 9, 2026, 12:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d97a9566e08190a92b49ce73963078 |
completed | April 10, 2026, 10:32 p.m. |
Created at: April 8, 2026, 9:08 p.m.