Triple

T2209194
Position Surface form Disambiguated ID Type / Status
Subject Primera Angostura E50873 entity
Predicate hasNavigationConstraint P12029 FINISHED
Object limited width for large vessels 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: limited width for large vessels | Statement: [Primera Angostura, hasNavigationConstraint, limited width for large vessels]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNavigationConstraint
Context triple: [Primera Angostura, hasNavigationConstraint, limited width for large vessels]
  • A. hasNavigationUse
    Indicates that something is used for navigation or serves a navigational function in relation to another entity.
  • B. hasNavigationAccess
    Indicates that one entity is permitted to access or use the navigation capabilities or navigation-related resources of another entity.
  • C. hasSemanticRestriction
    Indicates that a concept or relation is constrained in meaning or usage by specific semantic conditions or limitations.
  • D. hasNavigationHazard
    Indicates that something presents or contains a condition, object, or feature that poses a risk or obstacle to safe navigation.
  • E. constrainedBy chosen
    Indicates that one entity’s state, behavior, or possibilities are limited, restricted, or governed by another entity.
  • 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_69a88b06709c8190978fb2418470d1b6 completed March 4, 2026, 7:41 p.m.
NER Named-entity recognition batch_69abc1baa0948190b07ffc347a4f714e completed March 7, 2026, 6:12 a.m.
PD Predicate disambiguation batch_69abbda8a6dc8190aa855ce2d17194b1 completed March 7, 2026, 5:54 a.m.
Created at: March 4, 2026, 7:46 p.m.