Triple

T13570788
Position Surface form Disambiguated ID Type / Status
Subject Rutupiae E324153 entity
Predicate locatedNear P294 FINISHED
Object Richborough E335584 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: Richborough | Statement: [Rutupiae, locatedNear, Richborough]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Richborough
Context triple: [Rutupiae, locatedNear, 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 (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_69d80769100c819099111274614f5ed2 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbb00f5b8881908617f42d227ed137 completed April 12, 2026, 2:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69f77f8967288190b822ed1e115f85b2 completed May 3, 2026, 5:02 p.m.
Created at: April 9, 2026, 9:48 p.m.