Triple

T34740680
Position Surface form Disambiguated ID Type / Status
Subject City of Kodiak E1001487 entity
Predicate hasPortRank P20612 FINISHED
Object one of Alaska’s major commercial fishing ports 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: one of Alaska’s major commercial fishing ports | Statement: [City of Kodiak, hasPortRank, one of Alaska’s major commercial fishing ports]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPortRank
Context triple: [City of Kodiak, hasPortRank, one of Alaska’s major commercial fishing ports]
  • A. portRank chosen
    Indicates the relative importance or hierarchical ranking assigned to a port within a given system or context.
  • B. hasPortOn
    Indicates that one entity possesses or is located adjacent to a port situated on another specified geographic or infrastructural feature (such as a coast, river, or lake).
  • C. hasPortRole
    Indicates that an entity participates in a port with a specified functional or operational role.
  • D. hasHarborRanking
    Indicates the relative position or status of a harbor within an ordered ranking or evaluation system.
  • E. hasPorts
    Indicates that an entity is equipped with or provides access points (ports) for connection, communication, or interface with other entities or systems.
  • 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_69f76daf739881909ed3554f98a2b433 completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69ff2fbae9b48190847eefa1c227d43e completed May 9, 2026, 12:59 p.m.
PD Predicate disambiguation batch_69ff2f2218048190a32224a648182b5d completed May 9, 2026, 12:57 p.m.
Created at: May 3, 2026, 3:59 p.m.