Triple
T19299020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of New Orleans |
E482643
|
entity |
| Predicate | hasCruiseHomeportFor |
P51783
|
FINISHED |
| Object | Caribbean cruises |
—
|
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: Caribbean cruises | Statement: [Port of New Orleans, hasCruiseHomeportFor, Caribbean cruises]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCruiseHomeportFor Context triple: [Port of New Orleans, hasCruiseHomeportFor, Caribbean cruises]
-
A.
isCruisePort
Indicates that a location functions as a port where cruise ships dock, embark, or disembark passengers.
-
B.
isHomePortOf
chosen
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.
isPortOfCallFor
Indicates that a location serves as a scheduled stop or destination for a ship, vehicle, or journey.
-
D.
servesCruisePort
Indicates that one entity (typically a transportation service or route) provides service to or operates at a particular cruise port.
-
E.
isMainHarbourOf
Indicates that a harbour serves as the primary or principal port facility for a specified location or region.
- 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc8852208190ba0337a9623d9bdf |
completed | April 20, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:31 p.m.