Triple

T23282780
Position Surface form Disambiguated ID Type / Status
Subject Kemble railway station E588910 entity
Predicate near P350 FINISHED
Object Thames Head NE NERFINISHED

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: Thames Head | Statement: [Kemble railway station, near, Thames Head]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Thames Head
Context triple: [Kemble railway station, near, Thames Head]
  • A. Thames Head chosen
    Thames Head is the traditionally recognized spring in Gloucestershire, England, regarded as the starting point of the River Thames.
  • B. Thurne Mouth
    Thurne Mouth is the point in the Norfolk Broads where the River Thurne joins the River Bure, forming a notable junction for boating and navigation.
  • C. Bream Head
    Bream Head is a prominent coastal headland and scenic reserve at the entrance to Whangārei Harbour in Northland, New Zealand, known for its dramatic cliffs, native forest, and walking tracks.
  • D. Tottenham Lock
    Tottenham Lock is a canal lock on the River Lea in North London, used to manage water levels and enable boat navigation along the river.
  • E. Bablock Hythe
    Bablock Hythe is a historic riverside hamlet and former ferry crossing point on the River Thames in Oxfordshire, England.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e25d16e2c08190a291de254703129e completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f196447a748190bd797ec9baa63fc3 completed April 29, 2026, 5:25 a.m.
Created at: April 17, 2026, 4:58 p.m.