Triple

T17201929
Position Surface form Disambiguated ID Type / Status
Subject Minster-on-Sea E417495 entity
Predicate locatedNear P294 FINISHED
Object Queenborough E212159 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: Queenborough | Statement: [Minster-on-Sea, locatedNear, Queenborough]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Queenborough
Context triple: [Minster-on-Sea, locatedNear, Queenborough]
  • A. Queenborough chosen
    Queenborough is a small historic port town in Kent, England, situated on the Isle of Sheppey and known for its maritime heritage and medieval origins.
  • B. Roberttown
    Roberttown is a village in West Yorkshire, England, forming part of the town of Liversedge within the metropolitan borough of Kirklees.
  • C. Hildenborough
    Hildenborough is a village in Kent, England, situated near Tonbridge and known for its commuter links to London and surrounding towns.
  • D. Leybourne
    Leybourne is a village and civil parish in Kent, England, known for its residential character and proximity to the town of West Malling.
  • E. Coswig
    Coswig is a small town in the Free State of Saxony in eastern Germany, situated near the Elbe River between Dresden and Meißen.
  • 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_69d886d6ba8c819093215917b3d01689 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42db014b08190b88a5001e9f7811b completed April 19, 2026, 1:19 a.m.
NED1 Entity disambiguation (via context triple) batch_6a015fdc13d88190bbf9e6d1272814d2 completed May 11, 2026, 4:49 a.m.
Created at: April 10, 2026, 5:38 a.m.