Triple

T14726470
Position Surface form Disambiguated ID Type / Status
Subject Lechlade E345956 entity
Predicate isNavigationLimitOf P115533 FINISHED
Object River Thames for powered craft upstream 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: River Thames for powered craft upstream | Statement: [Lechlade, isNavigationLimitOf, River Thames for powered craft upstream]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isNavigationLimitOf
Context triple: [Lechlade, isNavigationLimitOf, River Thames for powered craft upstream]
  • A. isLimitOf
    Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
  • B. isNavigableVia
    Indicates that one entity can be reached, traversed, or accessed by means of another entity (such as a route, medium, or pathway).
  • C. isNavigableNear
    Indicates that an entity can be traversed or passed through in close proximity to another specified entity or location.
  • D. hasNavigationUse
    Indicates that something is used for navigation or serves a navigational function in relation to another entity.
  • E. navigableFrom
    Indicates that one location or entity can be reached or traversed from another, typically via a valid path, route, or connection.
  • F. None of above. chosen

Provenance (4 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_69d822e5911c8190ba589f957dbd9ba7 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec26013c8819090512f8b4df9cc87 completed April 14, 2026, 10:40 p.m.
PD Predicate disambiguation batch_69de657e174481909da0437556334a04 completed April 14, 2026, 4:04 p.m.
PDg Predicate description generation batch_69de716d3aac8190aaa6dc1f099b86e8 completed April 14, 2026, 4:55 p.m.
Created at: April 10, 2026, 1:29 a.m.