Triple
T5466761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulford |
E122729
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Amesbury |
E212097
|
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: Amesbury | Statement: [Bulford, near, Amesbury]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amesbury Context triple: [Bulford, near, Amesbury]
-
A.
Amesbury
chosen
Amesbury is a historic town in Wiltshire, England, best known for its proximity to the prehistoric monument of Stonehenge.
-
B.
Romsey
Romsey is a historic market town in Hampshire, England, known for its medieval abbey and riverside setting.
-
C.
Sherborne
Sherborne is a small rural village in West Oxfordshire, England, known for its traditional Cotswold stone buildings and picturesque countryside setting.
-
D.
Sherborne
Sherborne is a historic market town in southwest England renowned for its medieval abbey, castles, and well-preserved architecture.
-
E.
Malmesbury
Malmesbury is a historic market town in Wiltshire, England, renowned for its ancient abbey and status as one of the oldest continually inhabited towns in the country.
- 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_69bd4643f16081908d7f29e08096115a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9217009c819082631a2758b5f2a4 |
completed | March 20, 2026, 6:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf488da1d8819091e1cad0500b1747 |
completed | March 22, 2026, 1:40 a.m. |
Created at: March 20, 2026, 2:08 p.m.