Triple

T11312342
Position Surface form Disambiguated ID Type / Status
Subject Durrington, Wiltshire E267868 entity
Predicate hasNearbySettlement P4647 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: [Durrington, Wiltshire, hasNearbySettlement, Amesbury]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Amesbury
Context triple: [Durrington, Wiltshire, hasNearbySettlement, Amesbury]
  • A. Amesbury chosen
    Amesbury is a historic town in Wiltshire, England, best known for its proximity to the prehistoric monument of Stonehenge.
  • B. Amesbury
    Amesbury is a historic New England city in northeastern Massachusetts known for its early shipbuilding and industrial heritage along the Merrimack River.
  • C. Romsey
    Romsey is a historic market town in Hampshire, England, known for its medieval abbey and riverside setting.
  • D. Sherborne
    Sherborne is a historic market town in southwest England renowned for its medieval abbey, castles, and well-preserved architecture.
  • E. Sherborne
    Sherborne is a small rural village in West Oxfordshire, England, known for its traditional Cotswold stone buildings and picturesque countryside setting.
  • 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_69d6aaca5c24819083db46a30d86cb34 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e9c1b7dc81908d8cc768c47390d3 completed April 9, 2026, 6:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69e525c35538819085d76f7cdf362316 completed April 19, 2026, 6:58 p.m.
Created at: April 8, 2026, 9:32 p.m.