Triple
T16970729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fugglestone and Quidhampton |
E411668
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Quidhampton |
E1101337
|
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: Quidhampton | Statement: [Fugglestone and Quidhampton, hasPart, Quidhampton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Quidhampton Context triple: [Fugglestone and Quidhampton, hasPart, Quidhampton]
-
A.
Quidhampton
chosen
Quidhampton is a small village in Wiltshire, England, situated just west of Salisbury.
-
B.
Bothenhampton
Bothenhampton is a village in Dorset, England, situated just outside the market town of Bridport near the Jurassic Coast.
-
C.
Bockhampton
Bockhampton is a small settlement in Berkshire, England, forming part of the rural civil parish of Lambourn in the North Wessex Downs.
-
D.
Warminster
Warminster is a market town in Wiltshire, England, known for its historic architecture, surrounding countryside, and role as a local transport and service hub.
-
E.
Warminster
Warminster is a suburban township in Bucks County, Pennsylvania, known for its residential communities, local commerce, and small general-aviation airport.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0ac23a48190992fa125fceb1eb2 |
completed | April 18, 2026, 6:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00dc0b3d6c8190bc44afdd7a5a55f6 |
completed | May 10, 2026, 7:27 p.m. |
Created at: April 10, 2026, 5:31 a.m.