Triple
T15372380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyness Pier |
E367581
|
entity |
| Predicate | maritimeUse |
P49505
|
FINISHED |
| Object | inshore ferry operations |
—
|
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 ferry operations | Statement: [Lyness Pier, maritimeUse, inshore ferry operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritimeUse Context triple: [Lyness Pier, maritimeUse, inshore ferry operations]
-
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.
maritimeFunction
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.
-
C.
maritimeActivity
chosen
Indicates activities, operations, or behaviors that take place at sea or are directly related to maritime environments and navigation.
-
D.
usedInMaritimeNavigation
Indicates that something is employed as a tool, aid, or reference in the practice of maritime navigation.
-
E.
maritimeDomain
Indicates a relationship or activity that occurs within, affects, or is specifically associated with the maritime domain (seas, oceans, and related maritime 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e5c1d548190930bfaf0861595ae |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:18 a.m.