Triple

T21245097
Position Surface form Disambiguated ID Type / Status
Subject Bulford Kiwi E523584 entity
Predicate nearbySettlement P350 FINISHED
Object Amesbury 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: Amesbury | Statement: [Bulford Kiwi, nearbySettlement, Amesbury]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Amesbury
Context triple: [Bulford Kiwi, nearbySettlement, Amesbury]
  • A. Amesbury
    Amesbury is a historic New England city in northeastern Massachusetts known for its early shipbuilding and industrial heritage along the Merrimack River.
  • B. Amesbury chosen
    Amesbury is a historic town in Wiltshire, England, best known for its proximity to the prehistoric monument of Stonehenge.
  • C. Silchester
    Silchester is a small village in Hampshire, England, best known for the remains of the Roman town of Calleva Atrebatum.
  • D. Romsey
    Romsey is a historic market town in Hampshire, England, known for its medieval abbey and riverside setting.
  • 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 (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_69e0b513b89c81908b27147e91368db2 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e73599e5548190ad70d2c2bfa9e919 completed April 21, 2026, 8:30 a.m.
Created at: April 16, 2026, 3:47 p.m.