Triple
T26653195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greetsiel fishing harbour |
E666422
|
entity |
| Predicate | nauticalUse |
P49505
|
FINISHED |
| Object | inshore fishing |
—
|
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: inshore fishing | Statement: [Greetsiel fishing harbour, nauticalUse, inshore fishing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nauticalUse Context triple: [Greetsiel fishing harbour, nauticalUse, inshore fishing]
-
A.
maritimeUsage
Indicates the extent to which something is used for or involved in maritime activities, such as sea transport, navigation, or ocean-related operations.
-
B.
usedInMaritimeNavigation
Indicates that something is employed as a tool, aid, or reference in the practice of maritime navigation.
-
C.
usesAtSea
Indicates that something is employed, operated, or applied in a maritime or oceanic environment.
-
D.
maritimeActivity
chosen
Indicates activities, operations, or behaviors that take place at sea or are directly related to maritime environments and navigation.
-
E.
marineResources
Indicates a relationship where one entity possesses, provides, or is associated with marine-based resources (such as fish, minerals, or other ocean-derived materials) used or managed by another entity.
- 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_69ee9cf8c7188190b9b00270a8a89164 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6167ccb308190a3183b2145bf4ce8 |
completed | May 2, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:34 a.m.