Triple

T19706606
Position Surface form Disambiguated ID Type / Status
Subject River Thames at Oxford E473230 entity
Predicate hasStructure P35 FINISHED
Object Folly Bridge NE NERFINISHED

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: Folly Bridge | Statement: [River Thames at Oxford, hasStructure, Folly Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Folly Bridge
Context triple: [River Thames at Oxford, hasStructure, Folly Bridge]
  • A. Folly Bridge chosen
    Folly Bridge is a historic stone road bridge over the River Thames in Oxford, England, known for its distinctive arches and role as a key crossing near the city center.
  • B. Botolphs Bridge
    Botolphs Bridge is a small settlement in the Folkestone and Hythe District of Kent, England, situated near the Romney Marsh area.
  • C. Felton Bridge
    Felton Bridge is a historic stone road bridge in Northumberland, England, carrying traffic across the River Coquet near the village of Felton.
  • D. Sandfield Bridge
    Sandfield Bridge is a road bridge spanning the Gloucester and Sharpness Canal in Gloucestershire, England.
  • E. Lea Bridge
    Lea Bridge is an area in east London, England, known for its historic transport links and proximity to the River Lea and surrounding green spaces.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e516dd048190a0b6c93ea3e71f58 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e642bb5cd4819090e4c62bd74c4324 completed April 20, 2026, 3:14 p.m.
Created at: April 10, 2026, 1:46 p.m.