Triple

T14943554
Position Surface form Disambiguated ID Type / Status
Subject River Churn E372592 entity
Predicate hasName P744 FINISHED
Object River Churn E372592 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: River Churn | Statement: [River Churn, hasName, River Churn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: River Churn
Context triple: [River Churn, hasName, River Churn]
  • A. River Churn chosen
    River Churn is a tributary of the River Thames in Gloucestershire, England, flowing through the Cotswolds and the town of Cirencester.
  • B. River Ember
    The River Ember is a small watercourse in Surrey, England, that branches from and later rejoins the River Mole before flowing toward the River Thames.
  • C. Springwater
    Springwater is a rural township in central Ontario, Canada, known for its agricultural landscape and proximity to the city of Barrie.
  • D. River Burn
    River Burn is a small river in Norfolk, England, known for flowing through the village of Burnham Thorpe near the north Norfolk coast.
  • E. River Burn
    River Burn is a small river in North Yorkshire, England, known for flowing through Wensleydale before joining the River Ure.
  • 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_69d85cc9da0c81908d583ca3f63a3908 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded68c1df0819084c0cd61b207d398 completed April 15, 2026, 12:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe7e9484e8819086ca6a59d672e49d completed May 9, 2026, 12:23 a.m.
Created at: April 10, 2026, 2:38 a.m.