Triple

T11067305
Position Surface form Disambiguated ID Type / Status
Subject Seine maritime corridor E261657 entity
Predicate hasNavigationConstraints P47431 FINISHED
Object tidal conditions 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: tidal conditions | Statement: [Seine maritime corridor, hasNavigationConstraints, tidal conditions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNavigationConstraints
Context triple: [Seine maritime corridor, hasNavigationConstraints, tidal conditions]
  • A. hasNavigationStatus
    Indicates the current state or condition of an entity’s navigation, such as whether and how it is actively navigating.
  • B. hasNavigationUse
    Indicates that something is used for navigation or serves a navigational function in relation to another entity.
  • C. hasNavigationCharacteristic
    Indicates that an entity possesses a specific property, feature, or quality related to navigation or navigational behavior.
  • D. hasNavigationControl
    Indicates that one entity possesses authority or capability to direct, manage, or influence the movement or course of another entity.
  • E. hasAccessConstraint chosen
    Indicates that there is a limiting condition or rule governing the ability to access or use a particular resource, service, or action.
  • 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_69d6aa98650481908609c7c56bfa7902 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d79920428c81908db824ab54e08e8d completed April 9, 2026, 12:18 p.m.
PD Predicate disambiguation batch_69d74411d9e881908c0eeafa0f38e4b6 completed April 9, 2026, 6:15 a.m.
Created at: April 8, 2026, 9:26 p.m.