Triple

T1238477
Position Surface form Disambiguated ID Type / Status
Subject Grand Bridge E26601 entity
Predicate crosses P416 FINISHED
Object River Glyme E8424 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 Glyme | Statement: [Grand Bridge, crosses, River Glyme]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Glyme
Context triple: [Grand Bridge, crosses, River Glyme]
  • A. River Glyme chosen
    The River Glyme is a small river in Oxfordshire, England, that flows through the Cotswolds and the grounds of Blenheim Palace before joining the River Evenlode.
  • B. River Yarrow
    River Yarrow is a river in Lancashire, England, known for flowing through the towns of Chorley and Croston before joining the River Douglas.
  • C. River Yarrow
    The River Yarrow is a river in the Scottish Borders known for flowing through the scenic Yarrow Valley and its associations with Scottish history and ballad literature.
  • D. River Ogmore
    River Ogmore is a river in South Wales that flows through the town of Bridgend before reaching the Bristol Channel.
  • E. River Corve
    River Corve is a small river in Shropshire, England, that flows through rural countryside before joining the River Teme.
  • 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_69a4948689d08190b3a4a3f388c02148 completed March 1, 2026, 7:33 p.m.
NER Named-entity recognition batch_69a4bf406b988190a12aa26bbcb88d6a completed March 1, 2026, 10:35 p.m.
NED1 Entity disambiguation (via context triple) batch_69af2b42bb888190a0b16e3a59eb1175 completed March 9, 2026, 8:19 p.m.
Created at: March 1, 2026, 7:47 p.m.