Triple

T26103922
Position Surface form Disambiguated ID Type / Status
Subject The Nore anchorage E658486 entity
Predicate hasNavigationalFeature P172093 FINISHED
Object The Nore sandbank 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: The Nore sandbank | Statement: [The Nore anchorage, hasNavigationalFeature, The Nore sandbank]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNavigationalFeature
Context triple: [The Nore anchorage, hasNavigationalFeature, The Nore sandbank]
  • A. hasNavigationCharacteristic
    Indicates that an entity possesses a specific property, feature, or quality related to navigation or navigational behavior.
  • B. hasNavigationUse
    Indicates that something is used for navigation or serves a navigational function in relation to another entity.
  • C. hasNavigationPort
    Indicates that an entity is equipped with or connected to a navigation port used for directing or controlling movement or positioning.
  • D. isNavigableVia
    Indicates that one entity can be reached, traversed, or accessed by means of another entity (such as a route, medium, or pathway).
  • E. hasNavigationModel
    Indicates that an entity is associated with or uses a specific navigation model that defines how it determines or follows routes or paths.
  • 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_69ee5bc09c288190bc42a11972841383 completed April 26, 2026, 6:38 p.m.
NER Named-entity recognition batch_69f6a9603b208190b3533ea2b441514c completed May 3, 2026, 1:48 a.m.
PD Predicate disambiguation batch_69f6a751d5e48190a77dcecbe7ef9f0b completed May 3, 2026, 1:39 a.m.
PDg Predicate description generation batch_69f6a8de0b948190ae333e9cd99cbf6c completed May 3, 2026, 1:46 a.m.
Created at: April 26, 2026, 7:57 p.m.