Triple
T4562644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ocho Rios |
E121830
|
entity |
| Predicate | portOfCallFor |
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: [Ocho Rios, portOfCallFor, cruise ships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portOfCallFor Context triple: [Ocho Rios, portOfCallFor, 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.
portOfRegistryFor
Indicates that one entity serves as the official port where another entity (typically a vessel) is registered.
-
D.
lastEuropeanPortOfCall
Indicates the final European port at which a vessel or traveler stopped before departing for a non-European destination.
-
E.
isMainDeepWaterPortFor
Indicates that one location serves as the primary deep-water port facility for another entity, such as a region, city, or country.
- 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd582f21648190b49284eb61b618c9 |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.