Triple
T16419769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kastos |
E398783
|
entity |
| Predicate | hasPortOfCall |
P8160
|
FINISHED |
| Object | for sailing yachts in the Ionian Sea |
—
|
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: for sailing yachts in the Ionian Sea | Statement: [Kastos, hasPortOfCall, for sailing yachts in the Ionian Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPortOfCall Context triple: [Kastos, hasPortOfCall, for sailing yachts in the Ionian Sea]
-
A.
isPortOfCallFor
chosen
Indicates that a location serves as a scheduled stop or destination for a ship, vehicle, or journey.
-
B.
hasPortCity
Indicates that a place or region possesses or is associated with a city that functions as its port.
-
C.
previousPortOfCall
Indicates that a specified location was the last port where a vessel stopped or was registered before its current position or status.
-
D.
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.
-
E.
isCruisePort
Indicates that a location functions as a port where cruise ships dock, embark, or disembark passengers.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328f5c1bc8190a679f35bd6c0bc97 |
completed | April 18, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.