Triple

T18297856
Position Surface form Disambiguated ID Type / Status
Subject Sound of Jura E438279 entity
Predicate hasNavigationConcern P47583 FINISHED
Object requires careful pilotage 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: requires careful pilotage | Statement: [Sound of Jura, hasNavigationConcern, requires careful pilotage]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNavigationConcern
Context triple: [Sound of Jura, hasNavigationConcern, requires careful pilotage]
  • A. hasNavigationRoute
    Indicates that one entity provides or defines a navigation path or route leading to or through another entity.
  • B. hasNavigationStatus
    Indicates the current state or condition of an entity’s navigation, such as whether and how it is actively navigating.
  • C. hasNavigationUse
    Indicates that something is used for navigation or serves a navigational function in relation to another entity.
  • D. hasNavigationContext
    Indicates that an entity is associated with a particular navigation-related context or state that influences how it is accessed, viewed, or traversed.
  • E. hasNavigationCharacteristic chosen
    Indicates that an entity possesses a specific property, feature, or quality related to navigation or navigational behavior.
  • 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_69d8b915e3e881909125d760c15d0c29 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e5017cc540819096c103a2c72315e6 completed April 19, 2026, 4:23 p.m.
PD Predicate disambiguation batch_69e44fdf43d08190bbcfb6b1fe3cc0ee completed April 19, 2026, 3:45 a.m.
Created at: April 10, 2026, 10:35 a.m.