Triple

T35833655
Position Surface form Disambiguated ID Type / Status
Subject Port Network Authority of the Sea of Sardinia E1035868 entity
Predicate hasPortUnderAuthority P200056 FINISHED
Object Port of Cagliari NE NERFINISHED

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: Port of Cagliari | Statement: [Port Network Authority of the Sea of Sardinia, hasPortUnderAuthority, Port of Cagliari]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPortUnderAuthority
Context triple: [Port Network Authority of the Sea of Sardinia, hasPortUnderAuthority, Port of Cagliari]
  • A. hasNearbyPortAccess
    Indicates that an entity is located close enough to a port to feasibly use it for access or transport.
  • B. hasPortRole
    Indicates that an entity participates in a port with a specified functional or operational role.
  • C. 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).
  • D. hasUserPort
    Indicates that an entity is associated with, exposes, or is accessible through a specific user-facing port or interface.
  • E. hasPortUse
    Indicates that one entity utilizes or is assigned to a particular port for access, communication, or operation.
  • F. None of above. chosen

Provenance (4 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_69f76e192a94819082db360cb91e6a8d completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69ff6ef0d61c81909162d37c15a1a3c3 completed May 9, 2026, 5:29 p.m.
PD Predicate disambiguation batch_69ff6c6a58e08190921317062cd9d489 completed May 9, 2026, 5:18 p.m.
PDg Predicate description generation batch_69ff6eefa9c48190aac36916990f6db5 completed May 9, 2026, 5:29 p.m.
Created at: May 3, 2026, 4:06 p.m.