Triple

T19706609
Position Surface form Disambiguated ID Type / Status
Subject River Thames at Oxford E473230 entity
Predicate hasStructure P35 FINISHED
Object Osney Lock
Osney Lock is a lock on the River Thames in Oxford, England, used to manage river navigation and water levels near the city.
 E1390829 NE FINISHED

How this triple was built (4 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: Osney Lock | Statement: [River Thames at Oxford, hasStructure, Osney Lock]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Osney Lock
Context triple: [River Thames at Oxford, hasStructure, Osney Lock]
  • A. Cookham Lock
    Cookham Lock is a lock and weir on the River Thames in Berkshire, England, serving river traffic near the village of Cookham.
  • B. Nuneham Lock
    Nuneham Lock is a lock on the River Thames in Oxfordshire, England, serving river traffic near the village of Nuneham Courtenay.
  • C. Pyrford Lock
    Pyrford Lock is a historic lock on the River Wey Navigation in Surrey, England, used to manage water levels and enable boat passage along the waterway.
  • D. Radcot Lock
    Radcot Lock is a lock on the River Thames in Oxfordshire, England, used to manage river navigation and water levels near the village of Radcot.
  • E. Goring Lock
    Goring Lock is a lock and weir on the River Thames in England, helping to manage river navigation and water levels near the village of Goring-on-Thames.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Osney Lock
Triple: [River Thames at Oxford, hasStructure, Osney Lock]
Generated description
Osney Lock is a lock on the River Thames in Oxford, England, used to manage river navigation and water levels near the city.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Osney Lock
Target entity description: Osney Lock is a lock on the River Thames in Oxford, England, used to manage river navigation and water levels near the city.
  • A. Cookham Lock
    Cookham Lock is a lock and weir on the River Thames in Berkshire, England, serving river traffic near the village of Cookham.
  • B. Nuneham Lock
    Nuneham Lock is a lock on the River Thames in Oxfordshire, England, serving river traffic near the village of Nuneham Courtenay.
  • C. Pyrford Lock
    Pyrford Lock is a historic lock on the River Wey Navigation in Surrey, England, used to manage water levels and enable boat passage along the waterway.
  • D. Radcot Lock
    Radcot Lock is a lock on the River Thames in Oxfordshire, England, used to manage river navigation and water levels near the village of Radcot.
  • E. Goring Lock
    Goring Lock is a lock and weir on the River Thames in England, helping to manage river navigation and water levels near the village of Goring-on-Thames.
  • F. None of above. chosen

Provenance (5 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.
NED1 Entity disambiguation (via context triple) batch_6a07ab9aa85481909f57d914341b7468 completed May 15, 2026, 11:26 p.m.
NEDg Description generation batch_6a07ac97c68c819094b8013f6134ba8a completed May 15, 2026, 11:30 p.m.
NED2 Entity disambiguation (via description) batch_6a07ae88e76481908b9a6fda698eec12 completed May 15, 2026, 11:38 p.m.
Created at: April 10, 2026, 1:46 p.m.