Triple

T1280591
Position Surface form Disambiguated ID Type / Status
Subject River Great Ouse E27314 entity
Predicate flowsThrough P225 FINISHED
Object Ely E35525 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: Ely | Statement: [River Great Ouse, flowsThrough, Ely]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ely
Context triple: [River Great Ouse, flowsThrough, Ely]
  • A. Ely chosen
    Ely is a historic cathedral city in Cambridgeshire, England, renowned for its prominent Ely Cathedral and its location in the Fens.
  • B. Ipswich
    Ipswich is a historic town and port in Suffolk, England, known as one of the country’s oldest continuously inhabited settlements.
  • C. Haverhill
    Haverhill is a historic city in northeastern Massachusetts that functions as a suburban community within the Greater Boston metropolitan area.
  • D. Norwich
    Norwich is a historic cathedral city in Norfolk, England, known for its medieval architecture and role as a regional cultural and economic center.
  • E. Maidenhead
    Maidenhead is a large riverside town on the River Thames in Berkshire, England, known as a commuter hub for London with a mix of historic and modern development.
  • 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_69a496d3710c8190955dee8bc0dacb50 completed March 1, 2026, 7:43 p.m.
NER Named-entity recognition batch_69a4c094eb4881909a33061339f91190 completed March 1, 2026, 10:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69acbae45da48190832dd8d74fdb217a completed March 7, 2026, 11:55 p.m.
Created at: March 1, 2026, 7:50 p.m.