Triple

T4152820
Position Surface form Disambiguated ID Type / Status
Subject Basseterre E89945 entity
Predicate hasPortOfCallFor P8160 FINISHED
Object cruise ships 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: cruise ships | Statement: [Basseterre, hasPortOfCallFor, cruise ships]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPortOfCallFor
Context triple: [Basseterre, hasPortOfCallFor, cruise ships]
  • A. isPortOfCallFor chosen
    Indicates that a location serves as a scheduled stop or destination for a ship, vehicle, or journey.
  • B. isHomePortOf
    Indicates that a particular location serves as the primary base or port where a vessel or fleet is officially registered, stationed, or regularly returns.
  • C. hasPortCity
    Indicates that a place or region possesses or is associated with a city that functions as its port.
  • D. isCruisePort
    Indicates that a location functions as a port where cruise ships dock, embark, or disembark passengers.
  • E. hasFerryPort
    Indicates that a place serves as a location where ferries regularly dock to load and unload passengers or cargo.
  • 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_69aed95a59a881909b26e70b42c6811a completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af033ef6648190adde17f943d89c78 completed March 9, 2026, 5:28 p.m.
PD Predicate disambiguation batch_69af018c101081909070da5b11e5eb3d completed March 9, 2026, 5:21 p.m.
Created at: March 9, 2026, 3:44 p.m.