Triple

T10484469
Position Surface form Disambiguated ID Type / Status
Subject River Parrett E247260 entity
Predicate passesThrough P225 FINISHED
Object Langport E103132 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: Langport | Statement: [River Parrett, passesThrough, Langport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Langport
Context triple: [River Parrett, passesThrough, Langport]
  • A. Langport chosen
    Langport is a small historic market town in Somerset, England, known for its medieval heritage and strategic location by the River Parrett.
  • B. Frampton-on-Severn
    Frampton-on-Severn is a picturesque village in Gloucestershire, England, known for its large village green and historic Cotswold stone buildings.
  • C. Droitwich
    Droitwich is a historic spa town in Worcestershire, England, long known for its salt springs and brine baths.
  • D. Bridgwater
    Bridgwater is a historic market town in Somerset, England, known for its maritime heritage and role in regional trade and industry.
  • E. Stourport-on-Severn
    Stourport-on-Severn is a historic inland port town in Worcestershire, England, known for its canal basins and role in the development of the British canal network.
  • 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_69d381c309b88190af78aa681cf6a4c2 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d50968a0bc8190a18ba24eb37431d9 completed April 7, 2026, 1:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69d8a03c647c81909521fee4a66ec8ac completed April 10, 2026, 7:01 a.m.
Created at: April 6, 2026, 12:22 p.m.