Triple

T9147560
Position Surface form Disambiguated ID Type / Status
Subject Gravesend railway station E219494 entity
Predicate connectsTo P845 FINISHED
Object Rainham (Kent) E161424 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: Rainham (Kent) | Statement: [Gravesend railway station, connectsTo, Rainham (Kent)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rainham (Kent)
Context triple: [Gravesend railway station, connectsTo, Rainham (Kent)]
  • A. Rainham (Kent) chosen
    Rainham (Kent) is a suburban town in the Medway unitary authority of Kent, England, served by a railway station on routes into London.
  • B. Rainham
    Rainham is a suburban town in East London, England, known for its residential character and proximity to the River Thames.
  • C. Dagenham
    Dagenham is a suburban town in East London, historically known for its large Ford car plant and extensive post-war housing estates.
  • D. Hainault
    Hainault is a suburban area in northeast London, England, known for its residential character and proximity to Hainault Forest Country Park.
  • E. Gillingham and Rainham
    Gillingham and Rainham is a UK parliamentary constituency in the Medway area of Kent, represented in the 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_69ca83e121dc81909912bd66953081c5 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cca918a3c881909c34a6a682eb2625 completed April 1, 2026, 5:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69d0f36f72bc8190bf195a78bafcd873 completed April 4, 2026, 11:18 a.m.
Created at: March 30, 2026, 7:20 p.m.