Triple

T16153820
Position Surface form Disambiguated ID Type / Status
Subject Dinham Bridge E391982 entity
Predicate crosses P416 FINISHED
Object River Teme E52044 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 Teme | Statement: [Dinham Bridge, crosses, River Teme]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Teme
Context triple: [Dinham Bridge, crosses, River Teme]
  • A. River Teme chosen
    River Teme is a major river in Wales and western England known for its scenic rural course and role as a significant tributary of the River Severn.
  • B. River Thame
    River Thame is a tributary of the River Thames in southern England, flowing through Buckinghamshire and Oxfordshire before joining the Thames near Dorchester-on-Thames.
  • C. River Thur
    River Thur is a major river in northeastern Switzerland that flows through the canton of Thurgau before joining the Rhine.
  • D. Ave River
    The Ave River is a watercourse in northern Portugal that flows through the Minho region before emptying into the Atlantic Ocean near the city of Vila do Conde.
  • E. River Sowe
    The River Sowe is a tributary of the River Avon in the West Midlands of England, flowing through Warwickshire and the Coventry area.
  • 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_69d87f1c65e48190aa2b4c472e9bafc4 completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e21e57e95c8190ae4ed641be974ce5 completed April 17, 2026, 11:49 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0007833960819088334e10258a9d72 completed May 10, 2026, 4:20 a.m.
Created at: April 10, 2026, 5:01 a.m.