Triple

T6963295
Position Surface form Disambiguated ID Type / Status
Subject Rainham (Kent) E161424 entity
Predicate hasRailServiceTo P726 FINISHED
Object Chatham (Kent) E116735 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: Chatham (Kent) | Statement: [Rainham (Kent), hasRailServiceTo, Chatham (Kent)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chatham (Kent)
Context triple: [Rainham (Kent), hasRailServiceTo, Chatham (Kent)]
  • A. Chatham, Kent chosen
    Chatham, Kent is a historic town in southeast England, best known for its former Royal Navy dockyard and maritime heritage.
  • B. Kingston, Kent
    Kingston, Kent is a small historic village and civil parish in the county of Kent in South East England, situated near Canterbury.
  • C. Folkestone
    Folkestone is a coastal town and port in Kent, England, known as a gateway to continental Europe via the Channel Tunnel and nearby ferry links.
  • D. Chatham and Aylesford
    Chatham and Aylesford is a UK parliamentary constituency in Kent represented in the House of Commons.
  • E. Whitstable
    Whitstable is a coastal town on the north coast of Kent in southeast England, known for its historic oyster fishing industry and pebble beaches.
  • 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_69c68853cff881908439d488924a8283 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6daf197b0819085bd0433c8a7f716 completed March 27, 2026, 7:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69c761908564819084505f0ab1122a9c completed March 28, 2026, 5:05 a.m.
Created at: March 27, 2026, 2:30 p.m.