Triple

T11311993
Position Surface form Disambiguated ID Type / Status
Subject Gillingham, Kent E267858 entity
Predicate locatedNear P294 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: [Gillingham, Kent, locatedNear, Rainham, Kent]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rainham, Kent
Context triple: [Gillingham, Kent, locatedNear, 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. Medway, Kent
    Medway, Kent is a historic district in southeast England centered on the River Medway, known for its naval dockyards and maritime heritage.
  • D. Dagenham
    Dagenham is a suburban town in East London, historically known for its large Ford car plant and extensive post-war housing estates.
  • E. Hainault
    Hainault is a suburban area in northeast London, England, known for its residential character and proximity to Hainault Forest Country Park.
  • 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_69d6aaca5c24819083db46a30d86cb34 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e9c1b7dc81908d8cc768c47390d3 completed April 9, 2026, 6:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69e525c35538819085d76f7cdf362316 completed April 19, 2026, 6:58 p.m.
Created at: April 8, 2026, 9:32 p.m.