Triple

T10825647
Position Surface form Disambiguated ID Type / Status
Subject Iqaluit deep-water port (seasonal) E255491 entity
Predicate navigationalConstraint P12029 FINISHED
Object sea ice 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: sea ice | Statement: [Iqaluit deep-water port (seasonal), navigationalConstraint, sea ice]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: navigationalConstraint
Context triple: [Iqaluit deep-water port (seasonal), navigationalConstraint, sea ice]
  • A. navigationCondition
    Indicates the specific circumstances or requirements that must be satisfied for a navigation action or route to be valid or taken.
  • B. navigableFor
    Indicates that one entity (such as a path, route, or medium) can be traversed or used for movement by another entity (such as a vehicle, vessel, or agent).
  • C. designedToConstrain
    Indicates that one entity is intentionally created or configured to limit, restrict, or control the behavior, range, or properties of another entity.
  • D. constrainedBy chosen
    Indicates that one entity’s state, behavior, or possibilities are limited, restricted, or governed by 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.

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_69d6aa8081448190a9324184f2bd1c26 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d734d0389c819090a892693c4046ed completed April 9, 2026, 5:10 a.m.
PD Predicate disambiguation batch_69d70d1bf3648190b36fa96ea018e0dc completed April 9, 2026, 2:21 a.m.
Created at: April 8, 2026, 9:19 p.m.