Triple

T19124574
Position Surface form Disambiguated ID Type / Status
Subject Watling Street E468142 entity
Predicate connects P390 FINISHED
Object Richborough 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: Richborough | Statement: [Watling Street, connects, Richborough]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Richborough
Context triple: [Watling Street, connects, Richborough]
  • A. Richborough chosen
    Richborough is a historic site in Kent, England, known for its significant Roman remains and its role as a key gateway to Roman Britain.
  • B. Hildenborough
    Hildenborough is a village in Kent, England, situated near Tonbridge and known for its commuter links to London and surrounding towns.
  • C. Brigg
    Brigg is a small historic market town in North Lincolnshire, England, known for its traditional markets and rural character.
  • D. Harwich
    Harwich is a coastal town on southeastern Cape Cod in Massachusetts known for its beaches, harbors, and summer tourism.
  • E. Harwich
    Harwich is a historic port town in Essex, England, which once served as a parliamentary borough represented in the British House of Commons.
  • 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_69d8dd0796a48190b34ce4cd9d3f3be5 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5e3cb9d6c81908a8706c1f33a6378 completed April 20, 2026, 8:28 a.m.
Created at: April 10, 2026, 12:05 p.m.