Triple

T25934435
Position Surface form Disambiguated ID Type / Status
Subject Old Windsor Weir E653514 entity
Predicate managesReach P104809 FINISHED
Object reach between Bell Weir Lock and Romney Lock LITERAL 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: reach between Bell Weir Lock and Romney Lock | Statement: [Old Windsor Weir, managesReach, reach between Bell Weir Lock and Romney Lock]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: managesReach
Context triple: [Old Windsor Weir, managesReach, reach between Bell Weir Lock and Romney Lock]
  • A. manageThrough
    Indicates that one entity exercises control, direction, or administration over another entity or process by means of an intermediary entity, channel, or mechanism.
  • B. managingFor
    Indicates that one entity is responsible for directing, supervising, or overseeing activities, resources, or operations on behalf of another entity.
  • C. managementIs chosen
    Indicates that one entity holds a managerial role, responsibility, or authority over another entity.
  • D. managedIn
    Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
  • E. intendedReach
    Indicates the target audience, scope, or extent that something is meant or designed to affect or be accessible to.
  • F. None of above.

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_69e7ab3fd2f881908837305e4ba98011 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f65f7731e4819099d5bd3d915ee266 completed May 2, 2026, 8:32 p.m.
PD Predicate disambiguation batch_69f65c1f94ac8190bc6fbc7916fc0d82 completed May 2, 2026, 8:18 p.m.
Created at: April 22, 2026, 8:39 a.m.