Triple
T27479605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vesterø Havn |
E693562
|
entity |
| Predicate | maritimeTransportRole |
P59758
|
FINISHED |
| Object | regional ferry hub |
—
|
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: regional ferry hub | Statement: [Vesterø Havn, maritimeTransportRole, regional ferry hub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritimeTransportRole Context triple: [Vesterø Havn, maritimeTransportRole, regional ferry hub]
-
A.
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.
-
B.
vesselRoleIdentified
Indicates that the specific functional role or purpose of a vessel within a context (e.g., a system, process, or operation) has been determined and recorded.
-
C.
hasShipRole
Indicates that an entity holds or is assigned a specific role or function on a ship.
-
D.
transportationRole
Indicates a role or function that an entity has specifically in the context of providing, operating, or supporting transportation.
-
E.
maritimeUsage
Indicates the extent to which something is used for or involved in maritime activities, such as sea transport, navigation, or ocean-related operations.
- 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_69ef5381f2648190a2392d0fab833095 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 12:58 p.m.