Triple
T32425036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suzuka Port |
E828553
|
entity |
| Predicate | maritimeServiceType |
P59758
|
FINISHED |
| Object | coastal shipping |
—
|
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: coastal shipping | Statement: [Suzuka Port, maritimeServiceType, coastal shipping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritimeServiceType Context triple: [Suzuka Port, maritimeServiceType, coastal shipping]
-
A.
vesselTypeServedOn
Indicates the type of vessel on which an entity has served or performed duty.
-
B.
allowedSeaService
Indicates that an entity is permitted or authorized to perform or accrue service at sea.
-
C.
maritimeInfrastructureType
Indicates the specific kind of maritime infrastructure associated with or characterizing an entity (e.g., port, harbor, dock, or related facility).
-
D.
maritimeFunction
chosen
Indicates a relationship where an entity serves a role, purpose, or operational function specifically within maritime contexts such as sea transport, navigation, or marine activities.
-
E.
voyageType
Indicates the specific category or nature of a journey or trip that an entity undertakes.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 12:54 a.m.