Triple

T290363
Position Surface form Disambiguated ID Type / Status
Subject Kent E5977 entity
Predicate hasMajorTown P316 FINISHED
Object Tonbridge E32633 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: Tonbridge | Statement: [Kent, hasMajorTown, Tonbridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tonbridge
Context triple: [Kent, hasMajorTown, Tonbridge]
  • A. Tonbridge chosen
    Tonbridge is a historic market town in Kent, England, known for its medieval castle, riverside setting on the River Medway, and role as a local commercial and commuter hub.
  • B. Sevenoaks
    Sevenoaks is a commuter town in Kent, England, known for its historic market center, surrounding countryside, and proximity to London.
  • C. Walton-on-Thames
    Walton-on-Thames is a suburban town on the River Thames in southeast England, known for its commuter links to London and riverside amenities.
  • D. Banstead
    Banstead is a suburban town in southeast England known for its village-like high street and green spaces within the county of Surrey.
  • E. Weybridge
    Weybridge is a suburban town in southeast England known for its affluent residential areas and proximity to the River Thames and major transport links into London.
  • 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_69a25946a7ac8190a78871c210213272 completed Feb. 28, 2026, 2:56 a.m.
NER Named-entity recognition batch_69a25e4f78bc81909a64fd6aaec3b504 completed Feb. 28, 2026, 3:17 a.m.
NED1 Entity disambiguation (via context triple) batch_69a3faf81e108190b85040e8de93bfcb completed March 1, 2026, 8:38 a.m.
Created at: Feb. 28, 2026, 3:02 a.m.